Hacker News Reader

Comment by haroldp | Hacker News Reader

It seems like the one thing this doesn't/can't address is the IP shortage. Does help much if example.com is virtual hosted on the same IP address as 100 other sites?

View on HN

The SNI stuff (http://en.wikipedia.org/wiki/Server_Name_Indication) helps with this if you can do without XP support.

It's not really XP that's the problem, but IE6. Firefox and Chrome support SNI even if you run them on XP.

All IE versions on XP, alas.

And also Android 2.3 stock browser support.

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.

Python 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.)

Was surprised by this so just did a little research. It appears (https://stackoverflow.com/questions/18578439/using-requests-... , 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.

Note 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 has more information, too.

Are 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?

I 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".

Reply on news.ycombinator.com