-
Notifications
You must be signed in to change notification settings - Fork 1.9k
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Introduce UriCompliance.Violation.FRAGMENT
to reject HTTP Request Line that includes fragment section.
#11579
Comments
@joakime can you please reword everywhere you wrote "query" meaning "fragment"? |
UriCompliance.Violation.FRAGMENT
to reject HTTP Request Line that includes Query section.UriCompliance.Violation.FRAGMENT
to reject HTTP Request Line that includes fragment section.
Yeah, sorry, my mind was stuck on the exception message from the old PR ... jetty.project/jetty-core/jetty-http/src/main/java/org/eclipse/jetty/http/HttpURI.java Lines 1460 to 1461 in fed10f7
The exception messages from that commit showed up as ...
|
https://www.rfc-editor.org/rfc/rfc9110.html#section-7.1 says ignore/drop rather than reject?!? So perhaps we do not include this violation by default? |
Jetty version(s)
12.0.7
Jetty Environment
All
Java version/vendor
(use: java -version)
All
OS type/version
All
Description
While working PR #11496 the idea of not allowing FRAGMENT section in a Request Line was introduced.
It is good idea that seems to follow the HTTP spec.
Location
response header can contain a fragment indicatorIf we do this, we should be careful how we do it, and allow a configurable UriCompliance mode to configure the behavior.
See original commit (reverted in PR #11496):
fed10f7
The text was updated successfully, but these errors were encountered: