Timeline for Bad format returned by Stack Exchange API, not GZip?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| May 23, 2017 at 12:39 | history | edited | CommunityBot |
replaced http://stackoverflow.com/ with https://stackoverflow.com/
|
|
| Jul 14, 2013 at 4:35 | comment | added | balphaStaff♦ | Yes, that's what I said. Of course the JSON is UTF8-encoded. But treating the raw gzip data as UTF8 is what makes no sense. | |
| Jul 14, 2013 at 4:00 | vote | accept | Steve | ||
| Jul 14, 2013 at 4:00 | comment | added | Steve |
I was able to get it to work. Using UTF-8 encoding works fine. I had to change StreamReader and now work with byte[]s only until after I've unzipped the response.
|
|
| Jul 14, 2013 at 3:45 | comment | added | Steve |
The response has a ContentType of application/json; charset=utf-8.
|
|
| Jul 13, 2013 at 14:31 | history | answered | balphaStaff♦ | CC BY-SA 3.0 |