You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@synapse.apache.org by Qi...@csiro.au on 2008/07/16 02:32:35 UTC
Problem of "chunked Transfer-Encoding forbidden"
Hi, All
I have received "Length Required" error from one of my server. It seems
Synapse chopped off the Content-Lenght in the head.
How can I fix it up?
Another thing is the error "chunked Transfer-Encoding forbidden". Should
I change some settings of this server, or I can modify Synapse to match
the requirement of this sever?
Many thanks
Bai
HTTP/1.1 411 Length Required
Date: Wed, 16 Jul 2008 00:24:36 GMT
Connection: close
Transfer-Encoding: chunked
Content-Type: text/html; charset=iso-8859-1
164
<!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
<HTML><HEAD>
<TITLE>411 Length Required</TITLE>
</HEAD><BODY>
<H1>Length Required</H1>
A request of the requested method POST requires a valid
Content-length.<P>
chunked Transfer-Encoding forbidden: /awdi/wfs<P>
<HR>
<ADDRESS>Apache/1.3.34 Server at water.dpiw.tas.gov.au Port 80</ADDRESS>
</BODY></HTML>
Re: Problem of "chunked Transfer-Encoding forbidden"
Posted by "Asankha C. Perera" <as...@wso2.com>.
Hi Bai
I am copying this reply to your email address directly this time, as I
see that you have not yet subscribed for the user list to receive our
replies.. please refer to http://synapse.apache.org/mail-lists.html to
subscribe
> I have received "Length Required" error from one of my server. It seems
> Synapse chopped off the Content-Lenght in the head.
>
> How can I fix it up?
>
By default Synapse uses HTTP 1.1 - chunked encoding, to achieve best
performance.. if you want to drop down to HTTP 1.0 and the
Content-Length encoding, set the following property before you send it out
<syn:property name="FORCE_HTTP_1.0" value="true" scope="axis2" />
>
> Another thing is the error "chunked Transfer-Encoding forbidden". Should
> I change some settings of this server, or I can modify Synapse to match
> the requirement of this sever?
>
Well what is the server / server software? It would be performing
sub-optimally if it doesn't understand chunked content.. looking at
enabling HTTP 1.1 / chunking on your server software would be the best
option for you
asankha
--
Asankha C. Perera
WSO2 - http://wso2.org
http://esbmagic.blogspot.com