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.
与恶龙缠斗过久,自身亦成为恶龙;凝视深渊过久,深渊将回以凝视…