[
https://issues.apache.org/jira/browse/QPID-8728?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tomas Vavricka updated QPID-8728:
---------------------------------
Summary: [Broker-J] Add useLegacyUriCompliance to HTTP Management Plugin UI
configuration (was: [Broker-J] Add useLegacyUriCompliance to HTTP management
plugin UI configuration)
> [Broker-J] Add useLegacyUriCompliance to HTTP Management Plugin UI
> configuration
> --------------------------------------------------------------------------------
>
> Key: QPID-8728
> URL: https://issues.apache.org/jira/browse/QPID-8728
> Project: Qpid
> Issue Type: Improvement
> Components: Broker-J
> Affects Versions: qpid-java-broker-10.0.0
> Reporter: Marco Geri
> Priority: Minor
> Fix For: qpid-java-broker-10.0.1
>
>
> After upgrading to Broker-J 10.0.0, the Management Web UI no longer works
> correctly when exchanges or queues contain the ":" character in their names.
> For example, when using a queue named "mf:ALL", any REST call triggered by
> the Web UI results in the following error:
> {{HTTP ERROR 400 Ambiguous URI path encoding}}
> This issue did not occur in previous versions of Broker-J.
> The problem may be related to the upgrade of Jetty to version 12, which
> appears to handle path encoding more strictly.
> Steps to reproduce:
> # Create a queue or exchange with a ":" in the name (e.g., mf:ALL).
> # Open the Management Web UI.
> # Navigate to the details of the created resource.
> # The UI triggers REST calls that fail with HTTP 400.
> *Implementation*
> As noted in the comment, setting the {{useLegacyUriCompliance}} flag to
> {{true}} resolves the issue with ":" in exchange or queue names.
> Flag {{useLegacyUriCompliance}} was added to the HTTP Management Plugin UI
> configuration.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
