I mean ... after all HTTPUtils.post() already sends out the Header
field ... which is one of the major requirements in HTTP 1.1.
So doesn't this simply mean changing the value of HttpUtils.HTTP_VERSION
from "1.0" to "1.1"?
Jesus M. Salvo Jr. wrote:
Why does Apache SOAP use HTTP/1.0 and n
Why does Apache SOAP use HTTP/1.0 and not HTTP/1.1?
Although SOAP 1.1 did not indicate directly that HTTP/1.1 must be
supported, it sort of indirectly did by the examples and the HTTP
specification in the reference:
http://www.w3.org/TR/SOAP/#_Toc478383526
http://www.w3.org/TR/SOAP/#_Toc4783835
The Apache SOAP client always uses HTTP 1.0, never HTTP 1.1. If you
need HTTP 1.1 support, you would either need to write your own
transport or move to another implementation like Axis.
Axis is nearing its 1.1 release. I believe someone has submitted an
Axis filter that does gzip, although it
Hi,
I'm quite confused about the fact that no new release are expected.
I do need compression over HTTP 1.1, which is currently available in CVS.
Moving to AXIS would not resolve my problem, because Axis does not provide
this feature.
Should I use a nightly build version in production? Is it sta