also interesting: curl -I https://news.ycombinator.com HTTP/1.1 501 Not Implemented Server: nginx Date: Mon, 06 May 2013 04:31:05 GMT Content-Type: text/html Content-Length: 174 Connection: close don't see that one every day :)
[deleted]
HN supports SPDY
11–20 of 79 posts
Re: HN supports SPDY
#12Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304.
The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't support it.
[1] The way I consume HN is I load up HN once or twice a day, open up all the interesting links and their comment pages in new tabs, and then go back to work. Then when I have some downtime (most of which is on the weekend) I read through all the open tabs.
Re: HN supports SPDY
#13Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304. The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't…
Isn't that how everyone uses HN?
Re: HN supports SPDY
#14Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304. The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't…
Isn't that how everyone uses HN?
Maybe. In which case, all the more reason to do it!
Re: HN supports SPDY
#15umm, and does this mean there's some way to have HN load faster?
Re: HN supports SPDY
#16Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304. The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't…
Isn't that how everyone uses HN?
It seems much more sane, even when my machines have 8GB+ of RAM to simply have a "read later" bookmark folder on your bookmark bar^. I have my bookmark bar shown with single icon hot shortcuts, a blank folder with all my bookmarks and a simply "revisit" folder with articles, youtube videos, whatever to read during downtime. (I guess quite simply I don't trust my browser or session recovery enough to do that).
Plus, Chrome Sync means I get those free on my mobile too. Nice for when I'm stuck a waiting room or something.
Also, isn't there a whole class of "read it later" type services? Seems a bit much overhead for me.
^ tip, you can drag the padlock/favicon next to the URL right onto/into your "revisit" bookmark folder too, in case you didn't know
Re: HN supports SPDY
#17Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304. The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't…
That behavior shouldn't get you banned, but some of your requests will get dropped if you make too many too quickly.
You will see 304s for static resources, like images and CSS. Efficiently handling HEAD requests for dynamically generated pages is actually painful, and many frameworks support it by handling the request like a GET and just omitting the body. In our case, most pages contain fnids and will never be the same twice anyway.
Re: HN supports SPDY
#18Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304. The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't…
> The way I consume HN is I load up HN once or twice a day, open up all the interesting links and their comment pages in new tabs, and then go back to work.
By that time most pages are probably updated, so you wouldn’t get any 304s anyway.
Since recent update, Firefox behavior is to only reload restored tabs on demand. This avoids that issue.
https://blog.mozilla.org/blog/2012/06/05/firefox-has-a-redes...
Re: HN supports SPDY
#19Great! Now if only they would implement allowing HEAD requests and support for any of the various headers that would allow me to get a 304. The reason I ask is because every time my Safari crashes, if I have 50 HN tabs open (as I often do on by Friday [1]) I'll get IP banned from HN because Safari will do a GET request on each page, but it can't pass any of the headers necessary to get back a 304, because HN doesn't…
Isn't that how everyone uses HN?
This is why tldr.io is useful. I can get my HN lazy-tabs down to 40 per visit.
Re: HN supports SPDY
#20...which enables it to return "unknown or expred link" even faster. </sarcasm