Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
I am facing an issue with URL encoding when running XWiki behind the OPNWAF reverse proxy. XWiki pages can have "+" signs encoded as "%2B" in the URL (e.g., /xwiki/bin/view/a%2Bb/ for the page "a+b").
Currently, Apache's default canonization changes the request from "a%2Bb" to "a+b".
The backend XWiki server then decodes this as "a b" (a[space]b), which breaks the link and leads to a 404 error.
Describe the solution you'd like
I would like an option in the OPNWAF GUI (e.g., a checkbox or an advanced settings input field) that allows adding the nocanon parameter to the ProxyPass directive for a specific location or backend.
Additional context
The resulting Apache configuration should look like this:
<Location "/">
ProxyPreserveHost On
ProxyPass "balancer://b34d8dc4-4516-45ca-9f2e-458ae79ff18b/" nocanon
ProxyPassReverse "balancer://b34d8dc4-4516-45ca-9f2e-458ae79ff18b/"
</Location>
Important notices
Before you add a new report, we ask you kindly to acknowledge the following:
Is your feature request related to a problem? Please describe.
I am facing an issue with URL encoding when running XWiki behind the OPNWAF reverse proxy. XWiki pages can have "+" signs encoded as "%2B" in the URL (e.g., /xwiki/bin/view/a%2Bb/ for the page "a+b").
Currently, Apache's default canonization changes the request from "a%2Bb" to "a+b".
The backend XWiki server then decodes this as "a b" (a[space]b), which breaks the link and leads to a 404 error.
Describe the solution you'd like
I would like an option in the OPNWAF GUI (e.g., a checkbox or an advanced settings input field) that allows adding the nocanon parameter to the ProxyPass directive for a specific location or backend.
Additional context
The resulting Apache configuration should look like this: