Skip to content

proposal: net/http: header fields order #24375

Closed
@plambein

Description

@plambein

With reference to #19292, which was closed because no concrete problem could be defined, and #21853.

We have a transparant http proxy server, used for calculating statistics, not modifying requests.
When proxying http traffic, the http header fields order sent to the destination will always get scrambled (alphabetically sorted). This means any golang proxy server can easily be fingerprinted by looking at the header field order.

Keeping the original order will probably be hard to do? However if it could be defined, people could work around this by defining the default order of the user agent.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions