On Sat, May 19, 2012 at 8:40 PM, Hiranya Jayathilaka <[email protected]>wrote:
> On Fri, May 18, 2012 at 10:01 PM, Abid Khan <[email protected]> > wrote: > > > Hello Hiranya, > > > > That is too bad to hear, we are not in position to move to a later > version > > of Synapse, so what is the way out for us, please advise. > > > > You can try upgrading HTTP Core to the latest version (v4.1.4 I think). > +1. That known issue with HTTPS communication is fixed in HTTPCore 4.1.3 and above (and in Synapse 2.1). However, that particular issue occurred under very specific circumstances. Moreover, IIRC, it occurred while Synapse is trying to 'read' the response from an HTTPS server. Hence, I don't think it's what Abid is experiencing. The best way to verify this would be to carry out a simple test with Synapse 2.1 in the same environment and see whether the problem gets solved. Thanks, Sadeep > > Thanks, > Hiranya > > > > > > Thanks > > Abid > > > > -----Original Message----- > > From: Hiranya Jayathilaka [mailto:[email protected]] > > Sent: Thursday, May 17, 2012 12:06 PM > > To: [email protected] > > Subject: Re: how can I avoid this exception > > > > On Thu, May 17, 2012 at 9:30 PM, Abid Khan <[email protected]> > wrote: > > > > > Hello Paul, > > > > > > Thanks for prompt response, and what you are saying makes perfect > > > sense, the issue on my side turned out to be more serious. As in my > > > message below I was thinking server is sending a valid XML response > > > with (may be) invalid DOCTYPE. Which is not the case. > > > > > > The problem seems to be that Synapse is not able to send the complete > > > message when the server is SSL, which is if we are using an httpS url > > > instead of plain http. And since server is getting a malformed XML > > > from synapse it is throwing html-based error back. > > > > > > I am wondering whether synapse was tested with https or is there any > > > special thing I have to configure to support https. > > > > > > > IIRC this was a known bug in the HTTP core version used in old Synapse > > releases. > > > > Thanks, > > Hiranya > > > > > > > > > > Thanks, > > > Abid > > > > > > -----Original Message----- > > > From: Paul Fremantle [mailto:[email protected]] > > > Sent: Wednesday, May 16, 2012 9:43 PM > > > To: [email protected] > > > Subject: Re: how can I avoid this exception > > > > > > Abid > > > > > > I'm not an expert on this. Basically the XML parser is behaving as it > > > *should*. The question is can we get it to behave as it shouldn't :-) > > > > > > 1) I think there is a way to tell the StAX parser to ignore the > DOCTYPE. > > > I'm not sure if its possible to do this through Synapse into the > > > underlying StAX parser easily though. > > > > > > 2) If you aren't really doing any XML processing you could turn off > > > parsing completely > > > > > > 3) A complete hack I can think of is to use the message relay to parse > > > this as a binary, hack the message in place to avoid the problem, and > > > then use the builder mediator. > > > > > > Paul > > > > > > On Tue, May 15, 2012 at 3:57 PM, Abid Khan <[email protected]> > > wrote: > > > > > > > I did that; and the response is valid XML but the doctype is > > > > expected to be something like > > > > > > > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML/2.0//EN"> > > > > > > > > Instead of > > > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> > > > > > > > > > > > > > > > > PS: notice a forward slash before 2.0 in the correct one. > > > > > > > > The problem is that it will take very long time to go thru > > > > build/test cycle of that product, and if I can change that behavior > > > > in Synapse configuration that would help. > > > > > > > > Regards, > > > > Abid > > > > > > > > > > > > -----Original Message----- > > > > From: Paul Fremantle [mailto:[email protected]] > > > > Sent: Tuesday, May 15, 2012 6:16 AM > > > > To: [email protected] > > > > Subject: Re: how can I avoid this exception > > > > > > > > Abid > > > > > > > > A good approach is to put TCPMON in the middle to look at exactly > > > > what the server is responding to the Synapse engine. > > > > > > > > Paul > > > > > > > > On Tue, May 15, 2012 at 1:19 AM, Abid Khan <[email protected]> > > > wrote: > > > > > > > > > Hello all, > > > > > > > > > > I am getting following fault from synapse, It looks like the > > > > > application is sending back an protocol version that synapse > > > > > cannot accept, is there any way I can avoid this issue? > > > > > > > > > > > > > > > <soapenv:Fault > > > > > xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";><faultco > > > > > de xmlns:tns="http://www.w3.org/2003/05/soap-envelope > > > > ">tns:Receiver</faultcode><faultstring>org.apache.axis2.AxisFault: > > > > > org.apache.http.ProtocolException: Not a valid protocol version: > > > > > <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML > > > > > 2.0//EN"></faultstring></soapenv:Fault > > > > > > > > > > > > > > > Regards, > > > > > Abid Khan > > > > > > > > > > > > > > > > > > > > > -- > > > > Paul Fremantle > > > > Co-Founder and CTO, WSO2 > > > > Apache Synapse PMC Chair > > > > OASIS WS-RX TC Co-chair > > > > > > > > blog: http://pzf.fremantle.org > > > > [email protected] > > > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > > > > > > > > > -- > > > Paul Fremantle > > > Co-Founder and CTO, WSO2 > > > Apache Synapse PMC Chair > > > OASIS WS-RX TC Co-chair > > > > > > blog: http://pzf.fremantle.org > > > [email protected] > > > > > > "Oxygenating the Web Service Platform", www.wso2.com > > > > > > > > > > > -- > > Hiranya Jayathilaka > > Associate Technical Lead; > > WSO2 Inc.; http://wso2.org > > E-mail: [email protected]; Mobile: +94 77 633 3491 > > Blog: http://techfeast-hiranya.blogspot.com > > > > > > -- > Hiranya Jayathilaka > Associate Technical Lead; > WSO2 Inc.; http://wso2.org > E-mail: [email protected]; Mobile: +94 77 633 3491 > Blog: http://techfeast-hiranya.blogspot.com > -- Sadeep Jayasumana ** Email: [email protected]**** Mobile: +61 4 1468 8521
