We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Recently I started seeing this exception:
795: unexpected token at '' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/json-1.8.0/lib/json/common.rb:155:in `parse' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/json-1.8.0/lib/json/common.rb:155:in `parse' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/json-1.8.0/lib/json/common.rb:334:in `load' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/flickraw-0.9.6/lib/flickraw/api.rb:137:in `process_response' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/flickraw-0.9.6/lib/flickraw/api.rb:63:in `call' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/flickraw-0.9.6/lib/flickraw/api.rb:44:in `initialize' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/flickraw-0.9.6/lib/flickraw.rb:17:in `new' /usr/local/Cellar/ruby/2.0.0-p247/lib/ruby/gems/2.0.0/gems/flickraw-0.9.6/lib/flickraw.rb:17:in `flickr'
Looking at tcpdump it seemed to be failing on a POST to http://api.flickr.com/services/rest/ with a Content-Encoding: gzip response header.
http://api.flickr.com/services/rest/
Content-Encoding: gzip
In flickraw/api.rb it seems to be passing the body of the http response directly to process_response without gunzipping it.
The text was updated successfully, but these errors were encountered:
issue hanklords#64 - handling gzip responses
ee2ef6e
No branches or pull requests
Recently I started seeing this exception:
Looking at tcpdump it seemed to be failing on a POST to
http://api.flickr.com/services/rest/
with aContent-Encoding: gzip
response header.In flickraw/api.rb it seems to be passing the body of the http response directly to process_response without gunzipping it.
The text was updated successfully, but these errors were encountered: