Hacker News new | past | comments | ask | show | jobs | submit login

Like www.sec.gov, this website only sends compressed data, ignoring Accept-Encoding: identity as a means of disabling compression.



IME, most websites respond to the Accept-Encoding header, or at least send uncompressed data in the absence of it. I normally do not send this header and I almost always receive uncompressed data. Sometimes there are rare exceptions. (For these I excpetions usually test with Accept-Encoding: identity.) I am generally curious about these exceptions, hence the comment. At least once, the website operator responded indicating it was due to a configuration error.


I’m genuinely curious about your reasons to intentionally disable compression? Is there any scenario where gzip is too costly for your device?




Join us for AI Startup School this June 16-17 in San Francisco!

Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: