Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Use RFC-compliant HeaderValue type. #287

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

Use RFC-compliant HeaderValue type. #287

wants to merge 2 commits into from

Commits on Oct 28, 2024

  1. Use RFC-compliant HeaderValue type. 

    When "header-value" feature is enabled, a RFC-compliant HeaderValue
type is used instead of the previously used UTF-8 String type.

Since HTTP field values aren't UTF-8 encoded, using the String type
meant that a plugin would crash when valid, but obsolete, non-UTF-8
characters were present in HTTP headers and/or trailers.

This feature is currently optional to avoid breaking changes and to
help with migration, but it will become a default feature in v0.3.

The HeaderValue type is re-exported from the http crate.

Signed-off-by: Piotr Sikora <[email protected]>
    @PiotrSikora
    PiotrSikora committed Oct 28, 2024
    Configuration menu
    Copy the full SHA
    9e1c348 View commit details
    Browse the repository at this point in the history

Commits on Nov 3, 2024

  1. review: retain values from more forgiving hosts. 

    Signed-off-by: Piotr Sikora <[email protected]>
    @PiotrSikora
    PiotrSikora committed Nov 3, 2024
    Configuration menu
    Copy the full SHA
    0542a78 View commit details
    Browse the repository at this point in the history