[HTTPCLIENT-751] ProtocolSocketFactory to upgrade an unsecured connection to secured via TLS

• Type: New Feature
• Status: Resolved
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 5.4-alpha2
• Environment: Coded for Java 1.4.2, but interested parties should be able to make it work for less than that.
• Assignee: Unassigned
• Reporter: Stephen O'Neil Butler
• Created: 17/Feb/08 17:26
• Updated: 24/Sep/24 14:48
• Resolved: 29/Jan/24 13:16

Description

HTTP allows a client to upgrade its connection from an unsecured one to a secured one via the Upgrade header. This protocol component implements a mandatory upgrade. From RFC2817, section 3.2:

>> OPTIONS * HTTP/1.1
>> Host: example.bank.com
>> Upgrade: TLS/1.0
>> Connection: Upgrade
>>

<< HTTP/1.1 101 Switching Protocols
<< Upgrade: TLS/1.0, HTTP/1.1
<< Connection: Upgrade
<<

– send and complete the TLS handshake
– server answers the original OPTIONS request

<< HTTP/1.1 200 OK
<< Date: Sun, 17 Feb 2008 17:23:35 GMT
<< Server: Apache
<< Content-Length: 0
<< Content-Type: text/plain
<<

My reason for developing this protocol socket factory was to support secure IPP over the standard IPP port.

Issue Links

• causes: HTTPCLIENT-2344 HTTP/1.1 TLS Upgrade (RFC-2817) should not be default
• depends upon: HTTPCORE-158 Support for 'Upgrade' request header / 101 (Switching Protocols) response (as defined per RFC 2817)