[jira] Commented: (AXISCPP-899) tunnel https connections over http proxies

["nadir amra (JIRA)" <ax...@ws.apache.org>]

    [ https://issues.apache.org/jira/browse/AXISCPP-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12776660#action_12776660 ] 

nadir amra commented on AXISCPP-899:
------------------------------------

Merged the code into SVN code-base.  Will wait for testing feedback before marking complete.  The code was put into svn under revision  835067 (http://svn.apache.org/viewvc?view=revision&revision=835067).

There was some things that I did not do...in  HTTPTransport.cpp there were cases where "\r\n" was changed to "\n".  I did not do these updates. In addition, there was the case where: 

        // Now handle whether we are going to close connection after processing 
        // request. If HTTP/1.0 we have to always close the connection by default; otherwise,
        // we assume persistant connection by default.
        if( m_eProtocolType == APTHTTP1_0)
            m_bReopenConnection = true;

was changed to:

        // Now handle whether we are going to close connection after processing 
        // request. If HTTP/1.0 or HTTP/1.1 we have to always close the connection by
        // default; otherwise, we assume persistant connection by default.
        if( m_eProtocolType == APTHTTP1_0 || m_eProtocolType == APTHTTP1_1)
            m_bReopenConnection = true;

I am not sure why this was done....by default HTTP1.1 connection can be reused unless close was specified in header. 

> tunnel https connections over http proxies
> ------------------------------------------
>
>                 Key: AXISCPP-899
>                 URL: https://issues.apache.org/jira/browse/AXISCPP-899
>             Project: Axis-C++
>          Issue Type: New Feature
>          Components: Transport (Client)
>    Affects Versions:  1.6 Beta
>            Reporter: Franz Fehringer
>            Assignee: nadir amra
>         Attachments: AXISCPP-899.zip
>
>
> The necessary steps for this scheme would be (to my best knowledge)
> 1) connect normally to proxy
> 2) send http CONNECT request (with remote address as argument)
> 3) now we have a connection to the remote host (descriptor from step 1)
> 4) do SSL handshake
> 5) ready for normal SSL/HTTPS communication

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