One more thing.. When an HTTP/1.1 request is sent to Tomcat, it responds with an HTTP/1.1 message with "Transfer-Encoding: chunked ".
When an HTTP/1.0 request is sent to Tomcat, it responds with an HTTP/1.1 message with "Connection: close ". That means, even though it responds with an HTTP/1.1 message, it behaves as HTTP/1.0 kind of thing.. Thanks, ~Isuru On Sat, Oct 2, 2010 at 11:19 AM, Isuru Suriarachchi <is...@wso2.com> wrote: > > > On Sat, Oct 2, 2010 at 10:55 AM, Afkham Azeez <az...@wso2.com> wrote: > >> Charitha, >> Can you deploy Axis2 on Tomcat 5.5.23 and let us know what you are >> seeing? >> > > I did test this while ago and the issue is there in Axis2 on Tomcat case as > well. > > >> >> What version of TC did you deploy Axis2 on? >> > > I think Charitha has tested it using the Simple Axis2 server, in which case > Axis2 responds correctly. > > So the conclusion is, the issue exists in Tomcat HTTP transport. However, I > tested on Tomcat 5.5.20. Will test on some newer version.. > > Thanks, > ~Isuru > > >> >> Azeez >> >> >> >> On Sat, Oct 2, 2010 at 9:30 AM, Charitha Kankanamge <chari...@wso2.com>wrote: >> >>> When I send either Http-1.1 or 1.0 request to WSAS, it always responds >>> back with HTTP-1.1 [1] >>> >>> I tried with Axis2 server and it correctly responded back with Http 1.0 >>> in case of a 1.0 request. Is there any config property in WSAS in order to >>> enable HTTP 1.0 support? >>> >>> [1]https://wso2.org/jira/browse/CARBON-7810 >>> >>> Regards >>> Charitha >>> >>> Charitha Kankanamge >>> Senior Technical Lead, Manager QA >>> WSO2 Inc. >>> http://wso2.org >>> email: chari...@wso2.com >>> cell: +94 718 359 265 >>> blog: http://charithaka.blogspot.com >>> >>> wso2.com Lean Enterprise Middleware >>> >>> Disclaimer: This communication may contain privileged or other >>> confidential information and is intended exclusively for the addressee/s. If >>> you are not the intended recipient/s, or believe that you may have received >>> this communication in error, please reply to the sender indicating that fact >>> and delete the copy you received and in addition, you should not print, >>> copy, retransmit, disseminate, or otherwise use the information contained in >>> this communication. Internet communications cannot be guaranteed to be >>> timely, secure, error or virus-free. The sender does not accept liability >>> for any errors or omissions. >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Afkham Azeez* >> Senior Software Architect & Senior Manager; WSO2, Inc.; http://wso2.com, >> * >> * >> *Member; Apache Software Foundation; >> **http://www.apache.org/*<http://www.apache.org/> >> * >> email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 >> blog: **http://blog.afkham.org* <http://blog.afkham.org>* >> twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> >> * >> linked-in: **http://lk.linkedin.com/in/afkhamazeez* >> * >> * >> *Lean . Enterprise . Middleware* >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > Isuru Suriarachchi > Technical Lead & Product Manager, WSO2 Web Services Application Server > WSO2 Inc. http://wso2.com > email : is...@wso2.com > blog : http://isurues.wordpress.com/ > > lean . enterprise . middleware > > -- Isuru Suriarachchi Technical Lead & Product Manager, WSO2 Web Services Application Server WSO2 Inc. http://wso2.com email : is...@wso2.com blog : http://isurues.wordpress.com/ lean . enterprise . middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
