Hi,
I assume that you've deployed your Web service in Axis2 which is running in Websphere.
I guess you need to configure Websphere to response without chunked for HTTP 1.1
requests it. However I am unaware how to do it (or whether it can actually be done)
since it concerns configuring Webshere.
AFAIK, a Web service deployed in Tomcat always responses with Transfer-encoding
being
set to chunked irrespective of transfer encoding of the request and I don't
think
there is a configuration option to change that behavior. (However
Transfer-encoding header
was present in response)
HTH
Best,
Sanka
FFF7878 wrote:
Hi,
No, the Transfer-Encoding: chunked header is not present neither in the
request nor in the response.
I'm out of the office now until tuesday, so I won't be able to test any more
but the response header I gave in the first e-mail are still the one I get
when I disable HTTP chunking at runtime, in my web service just before
returning the response object to Axis2.
My servlet container is websphere, using PARENT_LAST classloading option...
Could this be the issue?
Thanks,
Pierre
keith chapman wrote:
No it cannot be a bug. Cause the content-length header is set by
commonsHTTPTransportSender and this is a basic use case. So I dont think
that its broken.
Do you see the following header in the response?
Transfer-Encoding: chunked
Thanks,
Keith.
On 10/3/07, FFF7878 <[EMAIL PROTECTED]> wrote:
I've disabled chunking in the service and the content-length is still not
included by Axis2 in the HTTP header.
Could it be an Axis2 1.3 bug?
Thanks,
Pierre
keith chapman wrote:
yes it would.
Thanks,
Keith.
On 10/3/07, FFF7878 <[EMAIL PROTECTED]> wrote:
Thanks for the answer.
Will Axis2 include the content-length value in the HTTP header if I
disable
the chunking by default? The client seems to be very dependant of this
header value!
Thanks in advance
Pierre
keith chapman wrote:
AFAIK chunking is true by default (When HTTP 1.1 is used) and if you
wanna
turn it off you have to specify it explicitly. Try this in your
service
MessageContext msgContext = org.apache.axis2.context
.MessageContext.getCurrentMessageContext().getOperationContext().getMessageContext(
WSDLConstants.MESSAGE_LABEL_OUT_VALUE );
msgContext.setProperty(HTTPConstants.CHUNKED,"false");
Thanks,
Keith.
On 10/3/07, FFF7878 <[EMAIL PROTECTED]> wrote:
Hello Axis users,
I have a web service integrated with Axis2 that communicates with
clients
using gSOAP. The problem is that the client don't receive the
complete
XML
response (sent in three TCP packets) when the WS is using Axis2
while
it
is
working when using Axis1.
HTTP 1.1 is used. In axis2.xml, i've disable chunking:
<transportSender name="http"
class="org.apache.axis2.transport.http.CommonsHTTPTransportSender">
<parameter name="PROTOCOL">HTTP/1.1</parameter>
<!--<parameter
name="Transfer-Encoding">chunked</parameter>--></transportSender>
here is the HTTP header request of the client:
POST /fsaDev/serverAuthent/SGPASupportWebService_0.2 HTTP/1.1
Host: www.tests.cleyris.com:443
User-Agent: gSOAP/2.7
Content-Type: text/xml; charset=utf-8
Content-Length: 1803
Connection: close
Accept-Encoding: gzip, deflate
SOAPAction: "productList"
The HTTP header of the response when using Axis2 doesn't contain
the
content-lenght field and is not using HTTP chucking:
HTTP/1.1 200 OK
Date: Wed, 03 Oct 2007 08:48:58 GMT
Server: Apache/2.0.53 (Fedora)
Set-Cookie: JSESSIONID=0000OdoS96XVEDu8V5P6L0hKSAt:-1; Path=/
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-Control: no-cache="set-cookie, set-cookie2"
Content-Type: text/xml; charset=utf-8
Content-Language: fr-FR
Connection: close
The content-length field is set when using Axis1:
HTTP/1.1 200 OK
Date: Thu, 27 Sep 2007 17:05:41 GMT
Server: IBM_HTTP_Server
Content-Length: 19181
Set-Cookie: JSESSIONID=0000MFbDWxjMj23LS6_ufCPTglH:-1; Path=/
Expires: Thu, 01 Dec 1994 16:00:00 GMT
Cache-Control: no-cache="set-cookie, set-cookie2"
Content-Type: text/xml; charset=utf-8
Content-Language: fr-FR
Connection: close
Is there a way to set the content length field? I'm not a HTTP
expert,
does
anybody see something strange?
Thanks in advance
Pierre
--
View this message in context:
http://www.nabble.com/-AXIS2--Content-length-not-set-in-header-tf4560984.html#a13016314
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
--
View this message in context:
http://www.nabble.com/-AXIS2--Content-length-not-set-in-header-tf4560984.html#a13023058
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
--
View this message in context:
http://www.nabble.com/-AXIS2--Content-length-not-set-in-header-tf4560984.html#a13023728
Sent from the Axis - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Keith Chapman
WSO2 Inc.
Oxygen for Web Services Developers.
http://wso2.org/
--
Sanka Samaranayake
WSO2 Inc.
http://www.bloglines.com/blog/sanka
http://www.wso2.org/
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
