4 ms·
Renderers and other "old technologies" has nothing to do with SSL. Typically you insert a reverse proxy in between the client and server to handle SSL encryptio
by mkonecny 12y ago
Renderers and other "old technologies" has nothing to do with SSL. Typically you insert a reverse proxy in between the client and server to handle SSL encryption on the fly - it is completely transparent to the server stack.
- pdkl95 12y agoIt could, in theory, be a problem if their HTML rendering software is generating a lot of absolute URLs that link back to the same host.
- judk 12y agoA college intern could debug that problem. It's a non-issue.
- rgbrgb 12y agoNot going to go into details but I'd guess you're underestimating the size of the codebase (and thus the complexity of certain site-wide changes) by at least two orders of magnitude. Imagine doing (and testing) a "simple change" for every project on Github for instance. This is the dark side of giving each of your dev teams freedom to pick their tools.