396414 - Support Upgrading to TLS Within HTTP/1.1 defined in RFC2817

Status: VERIFIED DUPLICATE of bug 276813

(Core :: Networking: HTTP, enhancement)

Description

[Linus van Geuns]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-GB; rv:1.8.0.12) Gecko/20070718 Fedora/1.5.0.12-4.fc6 Firefox/1.5.0.12
Build Identifier: 

If you connect to a webserver which requires 'Upgrading to TLS' for some ressource to be accessed by HTTP/1.1, Firefox and other Mozilla Products(?) cannot perform this 'Upgrade'.

It would be awsome to have RFC2817 support as the first browser out there(?)

Reproducible: Always

Steps to Reproduce:
1. Configure eg CUPS to secure a ressource by (Upgrade to) TLS
2. Try to access the ressource using Firefox
3. Enjoy the error message
Actual Results:  
Error Message

Expected Results:  
A TLS encryption of the HTTP(/1.1) connection

RFC2817

The following browsers failed to Upgrade to TLS:
- Firefox 1.5.0.12 (Fedora Core 6)
- Firefox 2.0.0.6 (Gentoo)
- IE7 (some Windows Terminal server)
- Safari 2.0.4 (Mac OS X 10.4.10)

Comment 2

[Linus van Geuns]

I'm Sorry, I posted this duplicate, but I explicitly searched for 'RFC2817' within all products and with all states, but didnt find one bug..

Comment 3

[Christian :Biesinger (don't email me, ping me on IRC)]

yeah, the other bug has a space after "RFC" :) I'd suggest searching for just the number next time.

Comment 4

[Linus van Geuns]

In fact, I searched for '2817', 'RFC2817', 'Upgrade'+'TLS', 'Upgrading to TLS'.
But never mind, I must have checked a wrond search criteria accidentally.