[ 
https://issues.apache.org/jira/browse/SYNAPSE-150?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Asankha C. Perera resolved SYNAPSE-150.
---------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.-RC1-B1
         Assignee: Asankha C. Perera  (was: Upul Godage)

When HTTP 1.0 was used with SSL, the SSLEngine was probably not writing all 
plain text output in one call - as per its documentation. Thus in 
ServerHandler.outputReady(..) method, we were incorrectly marking the encoder 
(The IdentityEncoder in this instance) as complete, when the outbuf still had 
more of the response to be written..

An additional check to check the outbuf seems to make sure that we wait for all 
data to be assed through before the encoder is informed of completion

        try {
            int bytesRead = source.read(outbuf);
            if (bytesRead == -1 && outbuf.position() == 0) {
                encoder.complete();
................

one of the interesting and time consuming defects of our 1.1 release.. fulled 
by an enthusiastic and persistent real user of Synapse :)!

> SSL returns headers but no response XML for POX POST from PHP. From Java, OK. 
> http POST from PHP, OK. SSL POST from PHP to Tomcat, OK
> -------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: SYNAPSE-150
>                 URL: https://issues.apache.org/jira/browse/SYNAPSE-150
>             Project: Synapse
>          Issue Type: Bug
>    Affects Versions: 1.0
>         Environment: JDK6 on RHEL3.
>            Reporter: Paul Anderson
>            Assignee: Asankha C. Perera
>             Fix For: 1.1.-RC1-B1
>
>
> When I use PHP to POST an http 1.0 POX request to Synapse by SSL, Synapse 
> replies with http response code and headers only, and then closes the 
> connection. No XML  is returned.
> Exactly the same PHP POST with plain http receives the XML.
> A Java command line SSL POST receives the XML.
> And PHP POSTing the data to a Tomcat JSP page over SSL works fine - it simply 
> receives HTML instead of XML.
> Seems to be something in the Synapse SSL code that is doing the wrong thing, 
> and silently.
> I tried setting non-blocking to false - no difference.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to