4 ms·
This really isn't a problem any more with SNI. With XP dying out, there's really no excuse anymore to not use it for shared hosting.
by silverwind 12y ago
This really isn't a problem any more with SNI. With XP dying out, there's really no excuse anymore to not use it for shared hosting.
- tedunangst 12y agoPython 2.7 (no SNI support) is the new Windows XP. Not a browser problem, but if you're building an API, it will lock people out. (sorry to beat a dead horse, but it's burned me recently and I think people are flipping the https only switch without awareness or consideration. doesn't mean "don't switch", but be aware.)
- cmwright 12y agoWas surprised by this so just did a little research. It appears (https://stackoverflow.com/questions/18578439/using-requests-with-tls-doesnt-give-sni-support/18579484#18579484 https://stackoverflow.com/questions/18578439/using-requests-... , http://docs.python-requests.org/en/latest/community/faq/#what-are-hostname-doesn-t-match-errors http://docs.python-requests.org/en/latest/community/faq/#wha...) that this is fixable in python 2.7 so not a show stopper, more of just a good to know.
- tedunangst 12y agoNote that many people don't use requests, which has a rather large dependency chain, and sometimes you don't have much choice. e.g., feedparser doesn't use requests, nor is it likely to because of the dependencies. PEP 466 https://www.python.org/dev/peps/pep-0466 https://www.python.org/dev/peps/pep-0466 has more information, too.
- kxo 12y agoAre you unable to throw any number of the faster, event-driven webservers/reverse proxies in front of Python 2.7 to satisfy your SNI needs?
- tedunangst 12y agoI am "able" to do lots of things, but running a reverse proxy just so a command line script works is outside the bounds of "willing".