Comment #4 on issue 4527 by funktopia: implement RFC 2817: Upgrading to TLS Within HTTP/1.1 http://code.google.com/p/chromium/issues/detail?id=4527
For what its worth, I would love to see this implemented From what I understand, it allows upgrading an http connection to https by sending a plain text header thus allowing http and https traffic to share the same port. However the reason myself and many others would be keen to see this implemented is because it would allow for the hosting of multiple secure sites on the same ip address and port. Currently, the web server has no way of knowing which domain is being requested when the request is made over ssl. Hence you can only distinguish between multiple ssl sites on the same ip address by using different ports which is obviously no good for sites intended for use by the general public. This means that individual ip addresses are needed for each site that requires ssl, which can cause a whole range of other difficulties. So whilst I appreciate that the benefit may be small in terms of the tangible effect for a typical user, for other web hosts like myself it would make a massive difference. -- You received this message because you are listed in the owner or CC fields of this issue, or because you starred this issue. You may adjust your issue notification preferences at: http://code.google.com/hosting/settings --~--~---------~--~----~------------~-------~--~----~ Automated mail from issue updates at http://crbug.com/ Subscription options: http://groups.google.com/group/chromium-bugs -~----------~----~----~----~------~----~------~--~---
