← Back to release summary

Sending custom per-request user-agent to HTTP proxies in CONNECT requests

Category
Network / Connectivity
Type
New or changed feature
Status
Deprecated (Chrome 73)
Intent stage
None

Summary

When establishing an HTTPS connection over an HTTP/HTTPS/H2/QUIC proxy, we send a CONNECT request with its own set of headers. Currently, if the original HTTPS request had a custom user-agent string, we would send that with the CONNECT request, rather than the default user-agent header. We plan to remove this behavior, and just use the configured global user-agent header.

Standards & signals

View on chromestatus.com