I want to send a compressed POST data with Javascript to a server I control. Is there any way to let the HTTP layer deal with the compression.
I'm sending JSON. If I set the content type to GZIP/deflate will the browser automatically compress it and then Apache with the deflate mod automatically decompress it so my application doesn't have to think about the data being compressed at all?
I know it can work the other way around but any way to make it work this way?
HTTP compression allows content to be compressed on the server before transmission to the client. For resources such as text this can significantly reduce the size of the response message, leading to reduced bandwidth requirements and download times.
HTTP data is compressed before it is sent from the server: compliant browsers will announce what methods are supported to the server before downloading the correct format; browsers that do not support compliant compression method will download uncompressed data.
The goal of HTTP compression is to reduce the size of certain resources that are transferred between a server and client. By reducing the size of web resources, compression can make more efficient use of network bandwidth.
Using gzip on the WebWhen a browser with gzip support sends a request, it adds “gzip” to its Accept-Encoding header. When the web server receives the request, it generates the response as normal, then checks the Accept-Encoding header to determine how to encode the response.
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.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With