You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
db_call = HTTParty.patch("https://[MYSUBDOMAIN].supabase.co/rest/v1/streets?street_name=Main", headers: {
"apikey": ENV['SUPABASE_SECRET_KEY'],
"Authorization": "Bearer #{ENV['SUPABASE_SECRET_KEY']}",
"Content-Type": "application/json",
"Prefer": "return=representation"
}, body: JSON.generate({"street_id": 12345})
puts db_call.response.body # Prints a bunch of gzipped gibberish
sio = StringIO.new( db_call.response.body )
gz = Zlib::GzipReader.new( sio )
puts gz.read() # Prints the actual content
My understanding from the docs is that HTTParty automatically uncompresses gzipped responses as long as I don't explicitly specify an Accept-Encoding request header.
Why is that not happening here?
P.S. FWIW, I just tried a very similar HTTParty POST call (rather than PATCH) and the response came back uncompressed as expected.
The text was updated successfully, but these errors were encountered:
I've run into this for a GET request. In my case the response includes a Range header, which causes Net::HTTP to not un-gzip the response automatically. Ideally I think HTTParty would automatically handle decompression of gzip data when Net::HTTP didn't handle it.
Using Ruby 3.0.4 and httparty 0.20.0
Here's an example API call:
My understanding from the docs is that HTTParty automatically uncompresses gzipped responses as long as I don't explicitly specify an
Accept-Encoding
request header.Why is that not happening here?
P.S. FWIW, I just tried a very similar HTTParty
POST
call (rather thanPATCH
) and the response came back uncompressed as expected.The text was updated successfully, but these errors were encountered: