hc-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Felix Schumacher (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (HTTPCLIENT-1712) SPNego Authentication to HTTPS service
Date Sun, 13 Mar 2016 19:54:33 GMT

    [ https://issues.apache.org/jira/browse/HTTPCLIENT-1712?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15192508#comment-15192508
] 

Felix Schumacher commented on HTTPCLIENT-1712:
----------------------------------------------

In my eyes the correct patch would be to revert the changes, but as the original poster may
have a valid case, I think it would be nice to make his wanted behaviour optional available.

What would be the preferred way to do introduce such an option?

> SPNego Authentication to HTTPS service
> --------------------------------------
>
>                 Key: HTTPCLIENT-1712
>                 URL: https://issues.apache.org/jira/browse/HTTPCLIENT-1712
>             Project: HttpComponents HttpClient
>          Issue Type: Bug
>          Components: HttpAuth
>    Affects Versions: 4.5.1
>            Reporter: Georg Romstorfer
>            Priority: Minor
>             Fix For: 5.0 Alpha1
>
>         Attachments: GGSSchemeBase.patch
>
>
> When connecting with the HttpClient to a website through the HTTPS-Protocol, SPNego Authentication
does not work, because in the method GGSSchemeBase#generateGSSToken is the service name hardcoded
to HTTP.
> A workaround is to extend the class SPNegoScheme and override this method.
> To fix this, I think it would be best to get the protocol from the current connection,
but I don't how to get the connection in this class, so I can't provide a patch.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@hc.apache.org
For additional commands, e-mail: dev-help@hc.apache.org


Mime
View raw message