-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
More debug to QUERY_STRING max length #1768
Labels
Comments
I wonder if we should log something other than the URL too. |
spk
added a commit
to spk/puma
that referenced
this issue
Jul 1, 2019
``` 2019-07-01 21:05:36 +0200: HTTP parse error, malformed request (/plop): #<Puma::HttpParserError: HTTP element QUERY_STRING is longer than the (1024 * 10) allowed length (was 20481)> ``` ref puma#1768
spk
added a commit
to spk/puma
that referenced
this issue
Jul 1, 2019
``` 2019-07-01 21:31:08 +0200: HTTP parse error, malformed request (127.0.0.1/plop): #<Puma::HttpParserError: HTTP element QUERY_STRING is longer than the (1024 * 10) allowed length (was 20481)> ``` ref puma#1768
spk
added a commit
to spk/puma
that referenced
this issue
Jul 1, 2019
``` 2019-07-01 21:31:08 +0200: HTTP parse error, malformed request (127.0.0.1/plop): #<Puma::HttpParserError: HTTP element QUERY_STRING is longer than the (1024 * 10) allowed length (was 20481)> ``` ref puma#1768
spk
added a commit
to spk/puma
that referenced
this issue
Jul 21, 2019
``` 2019-07-01 21:31:08 +0200: HTTP parse error, malformed request (127.0.0.1/plop): #<Puma::HttpParserError: HTTP element QUERY_STRING is longer than the (1024 * 10) allowed length (was 20481)> ``` ref puma#1768
nateberkopec
pushed a commit
that referenced
this issue
Jul 27, 2019
``` 2019-07-01 21:31:08 +0200: HTTP parse error, malformed request (127.0.0.1/plop): #<Puma::HttpParserError: HTTP element QUERY_STRING is longer than the (1024 * 10) allowed length (was 20481)> ``` ref #1768
Merged on master. |
Thanks |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
Make an HTTP query with a query string bigger than 1024*10
read the output of puma stderr
Expected behavior
The actual HTTP uri should be logged to know which query triggered the error
Actual behavior
The error message only shows the error and not the associated URI
System configuration
Ruby version: ruby 2.5.3p105
Rails version: Rails 4.2.11.1
Puma version: puma-3.12.0
The text was updated successfully, but these errors were encountered: