Hi, with the fix of TAP5-302 (URL encoded strings that contain symbols such as %2f (encoded "/") are decoded incorrectly in some environments) the URI encoding/decoding changed.
AFAICS URIs containing anything else than a-z, A-Z, 0-9 or one of -_.: are considered invalid. Therefore, when I have an URI that contains e.g. the '*' char, this is invalid. The URLEncoderImpl expects $002a as a representation for this char ($ + the four hex digits for this char). We're doing "custom" ajax calls and therefore need to build valid URIs in javascript (in terms of T5-URI-encoding). So I need to encode s.th. like "foo*bar" to "foo$002abar" Has anybody else this problem and has it solved already? Is there another / a better way to come around this URI encoding issue on the client side? Thx && cheers, Martin [1] https://issues.apache.org/jira/browse/TAP5-302
signature.asc
Description: This is a digitally signed message part
