Timeline for Keep getting HTTP 406
Current License: CC BY-SA 2.5
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 22, 2010 at 3:29 | history | edited | Kevin Montrose |
edited tags
|
|
| May 22, 2010 at 3:11 | comment | added | Franci Penov | @Kevin Montrose - you can mark this one as completed; it's been working properly whole day from corpnet. | |
| May 21, 2010 at 4:16 | history | edited | Franci Penov | CC BY-SA 2.5 |
added 121 characters in body
|
| May 21, 2010 at 3:39 | comment | added | Kevin Montrose | @lfount you and Franci should try again. The API will still respond with gzip'd (or deflate'd) content, but it won't throw a 406 back if a proxy strips it out along the way. Let me know if that solves your problem, as I'm afraid the "on SO at work" scenario may be pretty common... | |
| May 21, 2010 at 3:06 | vote | accept | Franci Penov | ||
| May 20, 2010 at 22:20 | history | edited | Franci Penov | CC BY-SA 2.5 |
added 54 characters in body
|
| May 20, 2010 at 17:48 | answer | added | carson | timeline score: 11 | |
| May 20, 2010 at 17:39 | comment | added | lfoust | I get this error from work (behind a corporate firewall) but not at home. I haven't yet found a workaround. | |
| May 20, 2010 at 17:25 | history | asked | Franci Penov | CC BY-SA 2.5 |