-
-
Notifications
You must be signed in to change notification settings - Fork 11k
check for all HTTP methods [branch master] #26968
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
check for all HTTP methods [branch master] #26968
Conversation
The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE) CLA: trivial
|
Ok with trivial for this |
t8m
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
OK with CLA: trivial
|
i don't understand the failing test... can someone give me a hint? |
It is unrelated to your PR. There is an intermittent issue which we are currently investigating. |
|
24 hours has passed since 'approval: done' was set, but as this PR has been updated in that time the label 'approval: ready to merge' is not being automatically set. Please review the updates and set the label manually. |
|
Merged to the master branch. Thank you for your contribution. |
The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE) CLA: trivial Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from #26968)
Instead of disabling the ssl filter and hand a fake request back to the core handler we should abort the connection directly. The current implementation allows to exhaust workers by sending HTTP requests on HTTPS port. Additionally the OpenSSL library doesn't detect HTTP PATCH, OPTIONS, DELETE and TRACE methods, so the current implementation is also buggy. See this openssl PR: openssl/openssl#26968
Shutdown the ssl filter instead of disabling it and create a fake request to pass it to the core filter. The current implementation allows to exhaust worker threads by sending HTTP on HTTPS. Additionally the Openssl library doesn't recognize the http methods PATCH, DELETE, OPTIONS and TRACE, so the current implementation only works partially. See the PR here: openssl/openssl#26968
Shutdown the ssl filter and abort the connection instead of disabling is and pass a fake request to the core handler. The current implementation allows to exhaust workers by sendin HTTP request to HTTPS port. Additionally the Openssl lib doesn't detect the http methods PATCH, DELETE, OPTIONS and TRACE. So the current implementation only works partially. See openssl PR: openssl/openssl#26968
The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE) CLA: trivial Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from openssl#26968)
The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE) CLA: trivial Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from openssl#26968)
The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE) CLA: trivial Reviewed-by: Tim Hudson <tjh@openssl.org> Reviewed-by: Tomas Mraz <tomas@openssl.org> (Merged from openssl#26968)
The change checks for all HTTP methods in ssl_record, not only GET, POST, PUT and HEAD. (additionally PATCH, DELETE, OPTIONS and TRACE)
CLA: trivial