Skip to content

proposal: net/url: adhere to RFC3986 #16127

@gmccue

Description

@gmccue

As detailed in #15891 , net/url does not properly follow RFC3986 when encoding URL strings. Certain characters, such as ( and ) are URL-encoded when they are not required to be by the RFC.

I propose updating the logic in net/url to allow for valid URL characters to remain un-encoded, possibly adding a new case statement for differentiating between escaping URL strings and encoding URL components.

Metadata

Metadata

Assignees

No one assigned

    Labels

    FrozenDueToAgeProposalWaitingForInfoIssue is not actionable because of missing required information, which needs to be provided.

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions