Compressing HTTP Post Data sent from browser

by

Will the browser automatically gzip-encode your data for you? The short answer is no.

The long answer is that some user-agents can do things like this, but you definitely can’t rely on it. The apache mod_deflate docs state:

some special applications actually do support request compression, for instance some WebDAV clients.

So, no, that’s not going to work. You’ll need to generate the appropriate HTTP request message yourself. The appropriate header in this case is Content-Encoding: gzip and NOT Content-Type: because the content itself is application/json, you’re just looking to encode the entity body of your HTTP request message for transport.

Note that you need to also add the appropriate Content-Length: header specifying the size in bytes of the message entity body after compression -OR- send your HTTP message using Transfer-Encoding: chunked and forego the content-length specification.

On the receiving end, you can instruct mod_deflate to use an input filter to decompress the information:

<Location /dav-area>
SetInputFilter DEFLATE
</Location>

This is a bit heavy handed if you’re only receiving compressed message bodies for a couple of resources. Instead, you should probably just use the client-side script to check for the Content-Encoding: gzip header and decompress the request body manually. How to do this in say, PHP, is another question entirely. If you need details for that you should post another question.

More Related Contents:

  1. Easy HTTP requests with gzip/deflate compression
  2. Why can’t browser send gzip request?
  3. What is the maximum length of a URL in different browsers?
  4. Do I need Content-Type: application/octet-stream for file download?
  5. What requests do browsers’ “F5” and “Ctrl + F5” refreshes generate?
  6. CORS with POSTMAN
  7. URL matrix parameters vs. query parameters
  8. Detecting the character encoding of an HTTP POST request
  9. Is a 302 redirect to relative URL valid, or invalid?
  10. ETag vs Header Expires
  11. Do I need a content-type header for HTTP GET requests?
  12. How can I get the clients IP address from HTTP headers?
  13. What is the limit on QueryString / GET / URL parameters
  14. What is the difference between URI, URL and URN? [duplicate]
  15. Is the URL fragment identifier sent to the server? [duplicate]
  16. How many socket connections can a web server handle?
  17. Comparing HTTP and FTP for transferring files
  18. What are proper status codes for CORS preflight requests?
  19. REST response code for invalid data
  20. How big can a user agent string get?
  21. URL hash is persisting between redirects
  22. How WebSocket server handles multiple incoming connection requests?
  23. Official references for default values of concurrent HTTP/1.1 connections per server? [closed]
  24. Does the HTTP Protocol support multiple content types in response headers?
  25. What is the http-header “X-XSS-Protection”?
  26. What is correct HTTP status code when redirecting to a login page?
  27. How to cancel a HTTPRequest in Angular 2?
  28. Is the Content-Length header required for a HTTP/1.0 response?
  29. Correctly switching between HTTP and HTTPS using .htaccess
  30. What is the difference between server side cookie and client side cookie?

Leave a Comment