Skip to content

WSGI server recv with no content-length key headers #138

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.

Sign up for GitHub

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

Jump to bottom
Closed
us3r64 opened this issue Jan 15, 2024 · 0 comments · Fixed by #137
Closed

WSGI server recv with no content-length key headers #138

us3r64 opened this issue Jan 15, 2024 · 0 comments · Fixed by #137

Comments

@us3r64
Copy link
Contributor

us3r64 commented Jan 15, 2024

When there is no content-length key in the request headers, asking for bytes from the socket is going to always timeout because there is no data or shouldn't any, since the no content-length.

Fix: #137
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Fix body recv when no content-length us3r64/Adafruit_CircuitPython_Wiznet5k
1 participant
@us3r64