-
-
Notifications
You must be signed in to change notification settings - Fork 31.4k
http.ServerResponse#strictContentLength = true
is broken
#57456
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
The issue is that you are passing the content-length value as a string, and its not being converted to number. |
Thanks. When setting headers with |
aduh95
pushed a commit
that referenced
this issue
Mar 23, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Apr 1, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Apr 1, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
to RafaelGSS/node
that referenced
this issue
Apr 8, 2025
PR-URL: nodejs#57458 Fixes: nodejs#57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Apr 14, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Apr 14, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
aduh95
pushed a commit
that referenced
this issue
Apr 14, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
aduh95
pushed a commit
that referenced
this issue
Apr 14, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
aduh95
pushed a commit
that referenced
this issue
Apr 15, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Apr 16, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
RafaelGSS
pushed a commit
that referenced
this issue
Apr 17, 2025
PR-URL: #57458 Fixes: #57456 Reviewed-By: Tim Perry <[email protected]> Reviewed-By: Paolo Insogna <[email protected]> Reviewed-By: James M Snell <[email protected]> Reviewed-By: Matteo Collina <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Version
v22.13.0
Platform
Subsystem
http
What steps will reproduce the bug?
How often does it reproduce? Is there a required condition?
Always.
What is the expected behavior? Why is that the expected behavior?
Should not throw error.
What do you see instead?
Additional information
No response
The text was updated successfully, but these errors were encountered: