We're updating the issue view to help you get more done. 

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:

1 1) http://test.opendap.org/opendap/w10n/data/nc/fnoc2.nc/u[0][0][0]?output=json

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

1 2) http://test.opendap.org/opendap/w10n/data/nc/fnoc2.nc/u%5B0%5D%5B0%5D%5B0%5D?output=json

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

Status

Assignee

Nathan Potter

Reporter

Nathan Potter

Labels

Story Points

None

Epic Link

Components

Sprint

None

Priority

Medium