Open Bug 1565292 Opened 6 years ago Updated 4 days ago

Consider using CONNECT for all (even non-secure) e2e requests to an HTTP(2) proxy

Categories

(Core :: Networking: Proxy, enhancement, P3)

Product:
Core
Component:
Networking: Proxy
Type:
enhancement

Tracking

()

Tracking Flags:
Tracking Status
firefox70 --- affected

People

(Reporter: mayhemer, Unassigned)

References

Details

(Whiteboard: [necko-triaged])

  • advantages:

    • general availability of 'tunnels' for anything, but I think we already have that
    • better and more trustworthy e2e conn error reporting

  • disadvantages:

    • added round trip/bug 1548796
    • more complexity added
    • need a new protocol proxy->browser to let the browser know that the proxy can do connect to any (or what) port(s)
    • and/or need a probe+fallback mechanism (more added complexity and round trips) for proxies that don't support this

Think of possible security implications when the proxy allows connection to any port (or wide range of ports)

Think of how this relates to RFC 8441.

Priority: -- → P3
Whiteboard: [necko-triaged]

Changing to corp confidential temporarily (till after Sept 10) on Tony and elan's request.

Group: mozilla-employee-confidential
Severity: normal → S3
Severity: normal → S3

Moving bug to Core/Networking: Proxy.

Component: Networking: HTTP → Networking: Proxy

Moving bug to Core/Networking: Proxy

Group: mozilla-employee-confidential
You need to log in before you can comment on or make changes to this bug.