Skip to content

Header normalization (yeah, again) #145

Closed
@meh

Description

@meh

I know this has already been discussed, but I want to talk about this again because it's causing me some useless trouble.

Why is the normalization done like this? The standard says that header names are case insensitive, but changing - to _ tends to break kind of everything. I sincerely think headers should be left untouched and make the #[] just use #downcase on the key, and really avoid NAME_OF_HEADER, beause it's non standard and in my proxy it breaks everything, and it's really useless to leave me renormalizing again every header at every request for no real good reason.

If I'm seeing this in the wrong way, please explain.

Quoting the HTTP RFC

Each header field consists of a name followed by a colon (":") and the field value. Applications ought to follow "common form", where one is known or indicated, when generating HTTP constructs, since there might exist some implementations that fail to accept anything

Making it accessible with NAME_OF_HEADER is ok, but changing the names to it is really non standard in my opinion.

Thanks for the time.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions