[
https://issues.apache.org/jira/browse/FELIX-6698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Paul Rütter (BlueConic) updated FELIX-6698:
-------------------------------------------
Fix Version/s: http.jetty12-1.0.4
> Ability to configure URI Compliance mode
> ----------------------------------------
>
> Key: FELIX-6698
> URL: https://issues.apache.org/jira/browse/FELIX-6698
> Project: Felix
> Issue Type: New Feature
> Components: HTTP Service
> Reporter: Paul Rütter (BlueConic)
> Priority: Major
> Fix For: http.jetty12-1.0.4
>
>
> See
> [https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-server-compliance-uri|https://eclipse.dev/jetty/documentation/jetty-12/programming-guide/index.html#pg-server-compliance-uri.]
> I'm running into an issue where URL's that worked in Jetty 9.x before, no
> longer work on Jetty 12.x (with Servlet API 6).
> It turns out that this behavior has changed in Jetty, and is configurable.
> When using LEGACY or UNSAFE, a workaround is needed to let Jetty handle the
> urls properly, besides setting the URI compliance mode.
> See
> [https://github.com/jetty/jetty.project/issues/11448#issuecomment-1969206031]
> for more information.
> I will put in a PR to get this configurable in Felix HTTP Jetty12.
> Example URL that no longer works:
> [https://domain.net/rest/v2/exampleEndpoint/76ffc12c-7d8b-433f-b95d-8ced9415a598/items/item_0_http%253A%252F%252Fwww.test.com%252F0.html]
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
