-
Bug
-
Resolution: Done
-
Major
-
3.0.16.Final
-
None
As a followup to RESTEASY-1099, when calling setRequestUri, the current query parameters aren't cleared, and new query parameters are merged into existing ones.
In my specific case (OAuth/OpenID Connect implementation, setRequestUri being called from a pre-matching filter to rewrite the URI depending on X-Forwarded-Proto), the problem is that having parameters appearing more than once is seen as an error (even if repeated with the same value). So my filter (see code snippet in RESTEASY-1099) is breaking my downstream resource by artificially duplicating the query parameters.
Note that the workaround highlights another bug: UriInfo.getQueryParameters returns mutable maps.
- is cloned by
-
JBEAP-4707 ContainerRequestContext setRequestUri doesn't clear previous query parameters
- Closed