ServiceGenerator.Utils.FetchDocument accepts and misinteprets compressed responses #271

Closed
GoogleCodeExporter opened this Issue Apr 14, 2015 · 2 comments

Comments

Projects
None yet
1 participant
What steps will reproduce the problem?
1. Run the service generator with a discovery URL (ServiceGenerator.exe url 
http://some/discovery/url)
2. Some servers may respond with gzip-compressed content
3. Fatal exception under JsonReader.Parse()

What is the expected output? What do you see instead?
Either prohibit non-identity encodings or check for and interpret them.

What version of the product are you using? On what operating system?
google-api-dotnet-client-1.2.4696-beta, Visual C# 2010, Windows 7

Please provide any additional information below.
This could be fixed by sending an additional request header:
Accept-Encoding: *;q=0, identity;q=1

Original issue reported on code.google.com by mvan...@google.com on 9 Nov 2012 at 10:57

Original comment by pele...@google.com on 10 May 2013 at 9:00

  • Changed state: Accepted
  • Added labels: Component-Build, Priority-Low
  • Removed labels: Priority-Medium
Old bug - we don't use the ServiceGenerator anymore. 

Original comment by pele...@google.com on 28 Nov 2013 at 5:59

  • Changed state: WontFix
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment