new encodingStyle attribute
Tom Scavo
trscavo at gmail.com
Mon Sep 17 11:14:56 EDT 2018
On Thu, Sep 13, 2018 at 3:40 PM Brent Putman <putmanb at georgetown.edu> wrote:
>
> https://google.github.io/guava/releases/20.0/api/docs/com/google/common/net/UrlEscapers.html
I assume you're using urlPathSegmentEscaper() in the case of the
<MetadataQueryProtocol> child element?
It's easier to list the ASCII characters that ARE escaped. Let me do
that for urlPathSegmentEscaper():
- space (irrelevant for entityIDs)
- double quote (")
- sharp (#)
- percent (%)
- less than (<)
- greater than (>)
- question mark (?)
- left square bracket ([)
- backslash (\)
- right square bracket (])
- caret (^)
and of course:
- slash (/)
I understand sharp, percent, question mark, and slash, but I'm not
sure why the others are needed?
The reason I ask is that changes to the MDQ spec might be needed. In
particular, the question mark seems to be a MUST-encode character
since there are entityIDs with query strings in the wild.
Tom
More information about the dev
mailing list