You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The fetch implementation we currently have seems to be somewhat outdated, leading to issues like this (forced lowercase header property names), while the standard has changed around that particular thing.
Prior to updating, needs extensive testing, since other changes might turn out to be backwards-incompatible.
Edit: this ticket is about fixing the fetch implementation around the header normalisation, so that property names are not forced to lowercase, according to the spec changes discussed in the linked ticket.
The text was updated successfully, but these errors were encountered:
@eksperts: Would you mind filling in an exhaustive list of the things you know needs fixing? Otherwise this will quickly end up as one of those tickets that can never be closed...
@kusma this lowercase-headers thing is the only one I'm aware of. Changing this ticket to "fix this one thing" then.
If we had the time, someone from engineering or features could evaluate what other changes have been implemented since our fetch implementation snapshot. Such task needs prioritisation, and I leave that to you.
eksperts
changed the title
Update fetch implementation
Update fetch implementation to solve forced lowercase header property names
Oct 5, 2017
The
fetch
implementation we currently have seems to be somewhat outdated, leading to issues like this (forced lowercase header property names), while the standard has changed around that particular thing.Prior to updating, needs extensive testing, since other changes might turn out to be backwards-incompatible.
Edit: this ticket is about fixing the fetch implementation around the header normalisation, so that property names are not forced to lowercase, according to the spec changes discussed in the linked ticket.
The text was updated successfully, but these errors were encountered: