Skip to content

store header char check too strict? #47479

Closed as not planned
Closed as not planned
@ronag

Description

@ronag

Not sure what is correct here but a test in undici started to fail in node 19 with:

Invalid character in header content ["content-disposition"]

With:

    res.writeHead(200, {
      'content-length': 2,
      'content-disposition': "attachment; filename='år.pdf'"
    })

I don't think å should cause problems?

Metadata

Metadata

Assignees

No one assigned

    Labels

    httpIssues or PRs related to the http subsystem.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions