[ 
https://issues.apache.org/jira/browse/AXIS2-2274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12477376
 ] 

jeff ling commented on AXIS2-2274:
----------------------------------

So you are working on httpclient, not Axis2? Then I guess this should be
assigned to someone else. Can you reassign this bug to someone else in Axis2
to fix the first (443 port) issue? The problem here is how does Axis2 knows
which port to stick in to the "state"? Since the https port can be changed,
how does httpclient find out which one to connect to? Anyway, you guys know
better.

Yes, the 2nd problem lies in httpclient.

Thanks,
Jeff



-- 
Jeff Ling
Product Solutions Engineer
GOOGLE
Office: (650) 253-3095
Fax: (650) 618-1835
Email: [EMAIL PROTECTED]


> Axis 2 as a client, access https:// doesn't work
> ------------------------------------------------
>
>                 Key: AXIS2-2274
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2274
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Bug
>          Components: transports
>    Affects Versions: 1.1
>            Reporter: jeff ling
>         Assigned To: Saminda Wishwajith Abeyruwan
>            Priority: Critical
>
> When the server is IIS, https doesn't work. https itself is supported through 
> Httpclient.
>                     The credential is put in to "state" as:
>                        agent.getState().setCredentials(new AuthScope(host, 
> port, realm), creds);
>                     The problem is that if it's https, real port is implied, 
> and the "port" here is the default "80". However, when the response comes 
> back, the actually port (usually 433) is returned. That caused the credential 
> (provider) not found. 
> This is only one of the issues. The credential handling code below is really 
> wrong:
>                 if (host != null) {
>                     if (domain != null) {
>                         /*Credentials for NTLM Authentication*/
>                         creds = new NTCredentials(username, password, host, 
> domain);
>                     } else {
>                         /*Credentials for Digest and Basic Authentication*/
>                         creds = new UsernamePasswordCredentials(username, 
> password);
>                     }
>                     agent.getState().setCredentials(new AuthScope(host, port, 
> realm), creds);
>                 } else {
>                     /*Credentials only for Digest and Basic Authentication*/
>                     creds = new UsernamePasswordCredentials(username, 
> password);
>                     agent.getState().setCredentials(new 
> AuthScope(AuthScope.ANY), creds);
>                 }
> First,  whether it's basic or Digest is not decided by whether domain name 
> exists, and realm applies to basic and digest, not integrated. If you look at 
> the IIS web server config screen, you will see. 

-- 
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