[
https://issues.apache.org/jira/browse/HTTPCORE-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Oleg Kalnichevski resolved HTTPCORE-158.
----------------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
5.0-alpha2
HttpCore now propagates intermediate (information) responses to message
exchange handlers and also provides an interface which enables HTTP/1.1 message
exchange handlers to start TLS session or switch to another protocol.
This should make it possible to implement transport security upgrade as per RFC
2817 or upgrade to WebSockets or HTTP/2 protocol.
Oleg
> Support for 'Upgrade' request header / 101 (Switching Protocols) response (as
> defined per RFC 2817)
> ---------------------------------------------------------------------------------------------------
>
> Key: HTTPCORE-158
> URL: https://issues.apache.org/jira/browse/HTTPCORE-158
> Project: HttpComponents HttpCore
> Issue Type: Improvement
> Components: HttpCore
> Reporter: Oleg Kalnichevski
> Fix For: 5.0-alpha2
>
>
> Presently HttpCore provides support for HTTP CONNECT method for establishing
> end-to-end tunnels across HTTP proxies as specified in the RFC 2817. However,
> HttpCore currently does not support 'Upgrade' / 101 (Switching Protocols)
> handshaking, which does not seem as widely used by the common HTTP agents and
> servers as HTTP CONNECT.
> Adding support for upgrading plain connections to TLS will require
> significant amount of work and is likely to call for non-trivial changes to
> the existing protocol handlers.
> We currently have no resources within the project to assign to this task, but
> will gladly assist an external contributor willing to work on adding support
> for 'Upgrade' / 101 (Switching Protocols) handshaking to HttpCore. This may
> also be a good topic for a Google Summer of Code project or a similar program.
> Oleg
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
