Transport phase not setting TRANSPORT_HEADERS in msgContext
-----------------------------------------------------------

                 Key: AXIS2-1985
                 URL: https://issues.apache.org/jira/browse/AXIS2-1985
             Project: Apache Axis 2.0 (Axis2)
          Issue Type: Bug
          Components: transports
    Affects Versions: 1.1.1, 1.2, nightly
         Environment: Windows XP SP2, jdk 1.5, Axis2 Nightly (Jan 5, 2007), 
Microsoft SQL Reporting Services 2005 
            Reporter: GNANASEKARAN VINAYAKAMURTHY


Transport Phase in Axis2 missed to parse the Http header from Input stream 
transport pipe

When I run axis2 client in debug mode, I could inspect the msgcontext object, 
which has Http header values as in the order of      
msgcontext-->operationContext-->properties-->TRANSPORT_IN-->AutoCloseInputStream-->watcher-->HttpMethodBase-->responseHeaders(HeaderGroup)-->Header

 And I think Transport Phase in Axis2 missed to parse the Http header(as in 
above) from input stream and thus missed not setting property TRANSPORT_HEADERS 
in msgContext.


We are trying to get cookie from Http header and we are not able to get the 
HTTP Header through msgContext.getProperty(MessageContext.TRANSPORT_HEADERS), 
since it returns NULL.

 Below is the soap response from the server (captured using tcpmon in client 
side) for your reference

***********************************************************************
HTTP/1.1 200 OK
Date: Thu, 11 Jan 2007 18:21:34 GMT
Server: Microsoft-IIS/6.0
MicrosoftOfficeWebServer: 5.0_Pub
X-Powered-By: ASP.NET
X-AspNet-Version: 2.0.50727
RSAuthenticationHeader: sqlAuthCookie
 
Set-Cookie: 
sqlAuthCookie=2E4D80C2D790C877650865B5FCD3E0F1DCC565C68BCCB22B3167B7063C61CBB11ED07D75F85354C1E56F17B46E6F3246D97F202C53424CA028F8DE4421BE498173FD58E42E8D2E55C3059167301E7E6C;
path=/; HttpOnly

Cache-Control: private, max-age=0
Content-Type: text/xml; charset=utf-8
Content-Length: 794
 
**************************************************

Any help that you guys can provide on this front will go a long way to 
promoting the Axis2 in our organization 
I would really happy to have this fixed and so that we would use Axis2 for our 
project, I would appreciate your help.


-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
https://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

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

Reply via email to