Timeline for Keep getting HTTP 406
Current License: CC BY-SA 2.5
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 21, 2010 at 3:06 | vote | accept | Franci Penov | ||
| May 21, 2010 at 2:01 | comment | added | Joel | On my home network this was caused by my ISP's web acceleration proxy. I found a way to bypass the proxy, but it may be more difficult in a corporate environment. | |
| May 20, 2010 at 18:38 | comment | added | Tim Post | I agree, mostly. There are some cases when HTTP proxies (especially in corporate offices where your browser comes loaded to trust the company CA, thus letting the proxy pretend to be secure.api.stackoverflow.com) also mangle https. Still, that would be a rare case. | |
| May 20, 2010 at 18:07 | comment | added | carson | I think an https endpoint would be a good compromise since it would bypass any firewall in between. If nothing else it would be nice to have at least one call exposed via https so this type of thing could be verified. | |
| May 20, 2010 at 18:01 | comment | added | Franci Penov | Yes, I am making the request from my corpnet, so you could be right. I also have the ISA Firewall Client, so I wonder if it could be the culprit. | |
| May 20, 2010 at 17:56 | comment | added | lfoust | I agree that it is fine to have compression on by default but I don't think allowing the ability to turn it off will really be wasting that much bandwidth. | |
| May 20, 2010 at 17:48 | history | answered | carson | CC BY-SA 2.5 |