On 04/06/2024 15:37, Christopher Schultz wrote:
On 6/4/24 09:10, Chuck Caldarale wrote:
<snip/>
The problem is the { and } characters.
My reading of RFC 7230 is that { and } /should/ be allowed, but
Tomcat's code rejects them by default.
My reading is as follows:
RFC 9110:
http-URI = "http" "://" authority path-abempty [ "?" query ]
RFC 3968:
path-abempty = *( "/" segment )
segment = *pchar
pchar = unreserved / pct-encoded / sub-delims / ":" / "@"
unreserved = ALPHA / DIGIT / "-" / "." / "_" / "~"
sub-delims = "!" / "$" / "&" / "'" / "(" / ")"
/ "*" / "+" / "," / ";" / "="
Neither '{' nor '}' are included in unreserved or sub-delims The are not
pct-encoded. Nor are they ':' or '@'. Therefore, there are not valid for
use in a segment. If you want to use them, they need to be pct-encoded.
While some of the text of RFC 3968, section 2.3 could be read as
suggesting other characters are included in unreserved, my reading of
that section is that the intended definition of unreserved is the
explicit definition I quoted above.
Mark
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org
