Why can’t browser send gzip request?

by

The client and server have to agree on how to communicate; part of this is whether the communication can be compressed. HTTP was designed as a request/response model, and the original creation was almost certainly envisioned to always have small requests and potentially large responses. Compression is not required to implement HTTP, there are both servers and clients that don’t support it.

HTTP compression is implemented by the client saying it can support compression, and if the server sees this in the request and it supports compression it can compress the response. To compress the request the client would have to have a “pre-request” that actually negotiated that the request would be made compressed OR it would have to require compression as a supported encoding for ALL requests.

* UPDATE Feb ’17 *
It’s been 8 years, but as @Phil_1984_ notes, a 3rd possible solution would be for the client and server to negotiate compression support and then use that for subsequent requests. In fact, things like HSTS work just this way with the client caching that the server expects to only speak TLS and ignore any unencrypted links. HTTP was explicitly designed to be stateless but we’ve moved beyond that at this point.

More Related Contents:

  1. Where can I find the default timeout settings for all browsers?
  2. What is the maximum length of a URL in different browsers?
  3. Are the PUT, DELETE, HEAD, etc methods available in most web browsers?
  4. How are parameters sent in an HTTP POST request?
  5. Do I need Content-Type: application/octet-stream for file download?
  6. What requests do browsers’ “F5” and “Ctrl + F5” refreshes generate?
  7. How to download multiple files with one HTTP request?
  8. CORS Access-Control-Allow-Headers wildcard being ignored?
  9. Easy HTTP requests with gzip/deflate compression
  10. Difference between Pragma and Cache-Control headers?
  11. HTTP GET in VBS
  12. How does “304 Not Modified” work exactly?
  13. Compressing HTTP Post Data sent from browser
  14. Using “transfer-encoding: chunked”, how much data must be sent before browsers start rendering it?
  15. Do web browsers always send a trailing slash after a domain name?
  16. Payloads of HTTP Request Methods
  17. Chunked transfer encoding – browser behavior
  18. Official references for default values of concurrent HTTP/1.1 connections per server? [closed]
  19. HTTP GET Request, ASP – I’m lost!
  20. How does url rewrite works?
  21. Does an HTTP Status code of 0 have any meaning?
  22. Detecting the character encoding of an HTTP POST request
  23. Is a 302 redirect to relative URL valid, or invalid?
  24. How can I get the clients IP address from HTTP headers?
  25. What is the difference between URI, URL and URN? [duplicate]
  26. How are cookies passed in the HTTP protocol?
  27. What is the http-header “X-XSS-Protection”?
  28. What is correct HTTP status code when redirecting to a login page?
  29. How to cancel a HTTPRequest in Angular 2?
  30. Correctly switching between HTTP and HTTPS using .htaccess

Leave a Comment