Backend response headers set issue #992

Open

Open

Backend response headers set issue#992

We had a report that this was causing duplication when using beresp.headers.set().

We should ensure we either properly guard or fix this case.

ContributorAuthor

Per the spec, this should be immutable, which should throw a TypeError on Headers.prototype.set.

linked a pull request that will close this issue

on Oct 11, 2024

fix!: immutable headers guards for incoming response and downstream request #1006

mentioned this

fix: ensure headers are set on first commit #1036

to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

fix!: immutable headers guards for incoming response and downstream requestfastly/js-compute-runtime

Participants