Timeline for Getting garbage on requests
Current License: CC BY-SA 2.5
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 8, 2010 at 23:54 | vote | accept | TheLQ | ||
| Oct 28, 2010 at 1:48 | history | edited | Kevin Montrose |
edited tags
|
|
| Oct 28, 2010 at 1:06 | answer | added | TheLQ | timeline score: 3 | |
| Oct 28, 2010 at 0:57 | comment | added | Kevin Montrose | I can't repro, have you tried decompressing the payload with gzip? Is it valid? | |
| Oct 28, 2010 at 0:40 | comment | added | TheLQ | @Kevin No, this is at my house. I updated the post with the HTTP headers | |
| Oct 28, 2010 at 0:39 | history | edited | TheLQ | CC BY-SA 2.5 |
added 1039 characters in body
|
| Oct 28, 2010 at 0:16 | comment | added | Kevin Montrose | Are you behind a proxy? Some proxies strip out Accept/Content-Encoding headers, which would cause your browser to not decompress the API responses. If you're not sure, you can test the theory by running what you get back from the API through gzip. | |
| Oct 28, 2010 at 0:00 | history | asked | TheLQ | CC BY-SA 2.5 |