w10n syntax collides with URI encoding rules enforced by recent Tomcat

Description

Recently Tomcat (>=8.5) began shipping with rules that cause it to reject requests in which the URL oath and query components are not correctly URI encoded. The w10n protocol utilizes a syntax which employs the square brackets as part of the URL path. Using % encoding on the square brackets in the URL did not resolve the problem - Tomcat returns a 400 stays header and nothing more.

Example:

This URL will be blocked by modern Tomcat because of the square brackets:

Changing the URL so that the square brackets are URI encoded did not help in my testing:

Probably we need to track down Thomas Huang or whoever is the w10n "owner" at NASA and find out what they are doing and/or what they think should be done

Environment

None

Activity

Show:
Nathan Potter
September 10, 2018, 9:54 PM
Edited

I worked through the examples and there were issues.
In the end I found that this URL won't work with Tomcat 8.5 or newer:

But once the square brackets are encoded it seems fine:

And this works for a curl command in a file (tested!):

Done

Assignee

Nathan Potter

Reporter

Nathan Potter

Labels

Epic Link

Components

Sprint

None

Priority

Medium
Configure