Error for requests with gzip content encoding and json content type #31

Activity

1. mendhak commented on Nov 12, 2021

   

   mendhak

   on Nov 12, 2021

   Owner

   More actions

   How can I recreate the issue? I tried this:

   curl -X POST -H "Content-Type: application/json" -d '{"a":"b"}' -H "Charset: utf-8" -H "Content-Encoding: gzip" http://localhost:8080/test/abc
   

   But everything seems fine.
2. oleg-babintsev commented on Nov 12, 2021

   

   oleg-babintsev

   on Nov 12, 2021

   Author

   More actions

   I think you need send content in gzip format as binary data, like this:

   echo '{ "mydummy" : "json" }' | gzip > body.gz
   curl -v -i http://localhost/mymodule -H'Content-Encoding: gzip' --data-binary @body.gz
   

   But I can't check it right now.
3. mendhak commented on Nov 15, 2021

   

   mendhak

   on Nov 15, 2021

   Last edited by mendhak

   Owner

   More actions

   I was able to recreate the error/message using

   echo '{ "mydummy" : "json" }' | gzip > body.gz
   curl -v -i http://localhost:8080/mymodule -H 'Content-Encoding: gzip' -H 'Content-Type: application/json' --data-binary @body.gz
   

   I then tried decompressing the body using body-parser, which is supposed to be able to work with gzip, but that didn't work.

   // parse application/x-www-form-urlencoded
   app.use(bodyParser.urlencoded({ extended: false }))
    
   // parse application/json
   app.use(bodyParser.json())
   

   I'll try it a bit more later. I'm looking for a solution that doesn't involve me writing custom code, to avoid complexity.
4. thieman commented on Feb 22, 2024

   

   thieman

   on Feb 22, 2024

   More actions

   This is a bug in the server, not something that needs to be fixed in the request. Amazon Data Firehose is an example of a well-known application that hits this bug when GZIP encoding is enabled.
5. matt-mercer

   added a commit that references this issue on Mar 19, 2025

   basic handling of gzip content-encoding on requests as per mendhak#31 …

   ...

   c4520e1
6. mendhak commented on Mar 22, 2025

   

   mendhak

   on Mar 22, 2025

   Owner

   More actions

   This is now available in mendhak/http-https-echo:36 thanks to @matt-mercer for the PR.
7. mendhak

   closed this as completedon Mar 22, 2025