On 11 August 2012 12:45, Andrej van der Zee <[email protected]> wrote: >> As far as I can tell, the HTTP implementations do not support >> compression of requests, only decompression of responses. > > The HTTP header "Content-Encoding" works both ways.
Yes. But it's up to the HTTP implementation whether it supports request compression or not. If it does compress a request, then of course it must set the appropriate Content-Encoding. As far as I can tell, none of the 3 HTTP implementations used by JMeter actually support request compression. And JMeter does not implement compression either. Though you can send arbitrary POST/PUT bodies by specifying a file and omitting the file Name parameter. > The key difference > is that for HTTP requests one must know beforehand if the server > supports decompression. How is that determined? > On the other hand, for HTTP responses the > client tells the server that it *may* compress by setting the HTTP > request header "Accept-Encoding", but the server does not have to (for > example if the server does not support compression of responses). > > Cheers, > Andrej > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
