Ruwan, The reason to use HTTP 1.0 is that the webservice I'm calling does not support the chunked encoding style.
Regards, Stefan. Ruwan Linton-3 wrote: > > stlecho wrote: >> Ruwan, >> >> I've created a Proxy that sends the requests to TCPMon (localhost:8444) >> and >> here is the result: >> POST http://localhost:8444 HTTP/1.1 >> host: localhost:9444 >> SOAPAction: urn://fsb.belgium.be/fphp/v3_0/findPerson >> Content-Type: text/xml; charset=UTF-8 >> Transfer-Encoding: chunked >> Connection: Keep-Alive >> User-Agent: Synapse-HttpComponents-NIO >> > Stefan, this implies that the request to the actual server is on HTTP > 1.1 could you please post your full configuration? and then I will try > to figure out the problem? > > Anyway, as Asankha suggested is there any specific requirement for you > to use HTTP 1.0? > > Thanks, > Ruwan >> Regards, Stefan. >> >> >> Ruwan Linton-3 wrote: >> >>> Hi Stefan, >>> >>> stlecho wrote: >>> >>>> Hi Ruwan, >>>> >>>> I've been trying to set this property with version 1.7beta2, but I'm >>>> not >>>> sure :o( that it works correctly. The connection between my client and >>>> FSB >>>> uses HTTP 1.1 (which is OK). I've activated the TRACE log level and the >>>> message received by the endpoint is logged, but not the message that >>>> gets >>>> send to the webservice endpoint. >>>> >>>> How can I verify that the proxy connects to the Target Endpoint with >>>> HTTP >>>> 1.0 ? >>>> >>>> >>> You may use either TCPMon or tcpdump (only if you are on unix) to >>> monitor the outgoing tcp message. >>> >>> Thanks, >>> Ruwan >>> >>>> Config: >>>> <syn:proxy name="FSB-Proxy-WsSecurity" transports="https http" >>>> startOnLoad="true" statistics="enable" trace="enable"><syn:target >>>> endpoint="FSB-WSSecurity-Test"><syn:inSequence><syn:log level="full" >>>> separator=","/></syn:inSequence><syn:outSequence><syn:log level="full" >>>> separator=","/><syn:property name="FORCE_HTTP_1.0" value="true" >>>> scope="axis2-client"/><syn:send/></syn:outSequence></syn:target><syn:publishWSDL >>>> uri="..."/><syn:policy key="policy-FSB" type="out"/></syn:proxy> >>>> >>>> Log: >>>> 11:52:15,583 DEBUG [main][HttpConnection] Open connection to >>>> localhost:9444 >>>> 11:52:16,052 DEBUG [main][header] >> "POST >>>> /esb/soap/FSB-Proxy-WsSecurity >>>> HTTP/1.1[\r][\n]" >>>> 11:52:16,067 DEBUG [main][HttpMethodBase] Adding Host request header >>>> 11:52:16,083 DEBUG [main][header] >> "Content-Type: >>>> text/xml;charset=UTF-8[\r][\n]" >>>> 11:52:16,083 DEBUG [main][header] >> "SOAPAction: >>>> urn://fsb.belgium.be/fphp/v3_0/findPerson[\r][\n]" >>>> 11:52:16,083 DEBUG [main][header] >> "User-Agent: Jakarta >>>> Commons-HttpClient/3.0.1[\r][\n]" >>>> 11:52:16,114 DEBUG [main][header] >> "Host: localhost:9444[\r][\n]" >>>> 11:52:16,114 DEBUG [main][header] >> "Content-Length: 1421[\r][\n]" >>>> 11:52:16,114 DEBUG [main][header] >> "[\r][\n]" >>>> 11:52:16,114 DEBUG [main][content] >> "<?xml version='1.0' >>>> encoding='UTF-8'?><soapenv:Envelope ..." >>>> 11:52:16,161 DEBUG [main][EntityEnclosingMethod] Request body sent >>>> 11:52:16,473 DEBUG [main][header] << "HTTP/1.1 200 OK[\r][\n]" >>>> 11:52:16,473 DEBUG [main][header] << "Server: >>>> Apache-Coyote/1.1[\r][\n]" >>>> 11:52:16,473 DEBUG [main][header] << "Content-Type: >>>> text/xml;charset=UTF-8[\r][\n]" >>>> 11:52:16,473 DEBUG [main][header] << "Transfer-Encoding: >>>> chunked[\r][\n]" >>>> 11:52:16,473 DEBUG [main][header] << "Date: Tue, 10 Jun 2008 09:48:16 >>>> GMT[\r][\n]" >>>> >>>> Regards, Stefan. >>>> >>>> >>>> Ruwan Linton-3 wrote: >>>> >>>> >>>>> Hi Stefan, >>>>> >>>>> You could force HTTP-1.0 to disable chunking, by setting the following >>>>> property at the axis2 scope; >>>>> >>>>> <property name="FORCE_HTTP_1.0" value="true" scope="axis2"/> >>>>> >>>>> Thanks, >>>>> Ruwan >>>>> >>>>> stlecho wrote: >>>>> >>>>> >>>>>> Hi, >>>>>> >>>>>> >>>>>>> We've recently had an issue with a Webservice that does not support >>>>>>> chunked >>>>>>> >>>>>>> >>>>>> encoding. With Axis2 we are able to control the chunked behavior: >>>>>> context.setProperty(HTTPConstants.CHUNKED,Constants.VALUE_FALSE); >>>>>> >>>>>> Is this functionality available with WSO2 ESB (<syn:property >>>>>> name="FORCE_CHUNKED_ENCODING" value="TRUE" scope="...") ? >>>>>> >>>>>> Regards, Stefan Lecho. >>>>>> >>>>>> >>>>>> >>>>> _______________________________________________ >>>>> Esb-java-user mailing list >>>>> [email protected] >>>>> http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >>>>> >>>>> >>>>> >>>>> >>>> >>>> >>> _______________________________________________ >>> Esb-java-user mailing list >>> [email protected] >>> http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user >>> >>> >>> >> >> > > > _______________________________________________ > Esb-java-user mailing list > [email protected] > http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user > > -- View this message in context: http://www.nabble.com/Control-chunked-encoding-tp16092138p17757381.html Sent from the WSO2 ESB Users mailing list archive at Nabble.com. _______________________________________________ Esb-java-user mailing list [email protected] http://wso2.org/cgi-bin/mailman/listinfo/esb-java-user
