Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
RFC: `Content-Length` on Response should be taken into account?
See original GitHub issuenode-fetch currently completely ignoring Content-Length header while consuming response.
Fetch specification about handling Content-Length on server response says almost nothing:
https://fetch.spec.whatwg.org/#concept-http-network-fetch (see https://github.com/whatwg/fetch/issues/67)
On other hand, we have a fetch-node specific extension to limit the size of the response.
My proposal - analyze and throw early when size for response is specified and Content-Length of response is greater than it.
Issue Analytics
- State:
- Created 3 years ago
- Reactions:1
- Comments:8 (1 by maintainers)
Top Results From Across the Web
Top Related Medium Post
Top Related StackOverflow Question
Troubleshoot Live Code
Top Related Reddit Thread
Top Related Hackernoon Post
Top Related Tweet
Top Related Dev.to Post
Top Related Hashnode Post
size was also one of those things that where added way back before AbortController existed and it was not possible to abort a request
I don’t quite agree on this change. Anything that hides what is actually there in actual responses. Even if it’s invalid, too large a body, it should be able to be seen.