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
StarlingMonkey recently started setting content-length and content-type in this position, but I believe this is a bug as content-length should only be sent when initiating the response.
Should we be setting content-length further, or does XQD effectively handle this for us entirely?
Corrected from original post after verifying content-type is certainly being set correctly.
The text was updated successfully, but these errors were encountered:
guybedford
changed the title
content-length and content-type
Auto content-type setting
Aug 2, 2024
guybedford
changed the title
Auto content-type setting
Auto content-length and content-type setting
Aug 2, 2024
guybedford
changed the title
Auto content-length and content-type setting
Auto content-length setting
Aug 2, 2024
We currently set
content-type
automatically duringextract_body
which is called in the request and response constructors.According to the fetch spec,
content-length
is supposed to be set when initiating the request, , see here - https://fetch.spec.whatwg.org/#http-network-or-cache-fetch.StarlingMonkey recently started setting
content-length
andcontent-type
in this position, but I believe this is a bug as content-length should only be sent when initiating the response.Should we be setting
content-length
further, or does XQD effectively handle this for us entirely?Corrected from original post after verifying
content-type
is certainly being set correctly.The text was updated successfully, but these errors were encountered: