You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
however, since the service expects a url-encoded timestamp, it fails.
the behavior i think would be good would be to either automatically url-encode all values, or at least make the incoming value equal to the outgoing one, like
I've found this to be an issue when substituting email addresses like [email protected].
Using the above example, the URL-encoded go link go/service-123/foo%2Bbar%40foo.com gets redirected to http://www.service123.com/pageA?param=foo+bar%40foo.com: the @ stays URL-encoded but the plus sign does not. The service then gets the param value with a space instead of a plus sign: foo [email protected].
given the a link like
go/service-123/%s
that expands to
http://www.service123.com/pageA?param=%s
if i supply a url-encoded value (i.e. a timestamp
2024-09-30T17:46:38+00:00
encoded as2024-09-30T17%3A46%3A38%2B00%3A00
) so the link looks likego/service-123/2024-09-30T17%3A46%3A38%2B00%3A00
when the link expands, the value has been url-decoded to
http://www.service123.com/pageA?param=2024-09-30T17:46:38+00:00
however, since the service expects a url-encoded timestamp, it fails.
the behavior i think would be good would be to either automatically url-encode all values, or at least make the incoming value equal to the outgoing one, like
http://www.service123.com/pathA?param=2024-09-30T17%3A46%3A38%2B00%3A00
The text was updated successfully, but these errors were encountered: