Skip to content
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

Long GET requests getting trimmed resulting in connection reset #33

Open
ozjimbob opened this issue Oct 3, 2016 · 0 comments
Open

Long GET requests getting trimmed resulting in connection reset #33

ozjimbob opened this issue Oct 3, 2016 · 0 comments

Comments

@ozjimbob
Copy link

ozjimbob commented Oct 3, 2016

We' re having an issue with Rook handling long GET requests longer than 1024 bytes - the request doesn't complete, resulting in a no response being returned. The problem essentially seems equivalent to this nginx issue, but there doesn't seem to be anywhere in Rook where that buffersize of 1024 is set: http://stackoverflow.com/questions/22697584/nginx-uwsgi-104-connection-reset-by-peer-while-reading-response-header-from-u

@ozjimbob ozjimbob changed the title Long GET requests getting concatenated resulting in connection reset Long GET requests getting trimmed resulting in connection reset Oct 3, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant