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
Currently, I have an issue that prevents usage of the last version of httpx:
I have a URL stored as an str object, that I wish to process;
That URL contains a query, with a query parameter that is itself an URL containing query parameters. In order to make the specification of that str possible, the query parameters from the URL need to be encoded. However, as slashes are not requiredhave naturally been re-encoded, in which slashes have not been encoded (http://host/path?sub_url=https://other?a%3Db%26c%3Dd);
httpx double encodes the already existing % characters, sending the http://host/path?sub_url=https:%2F%2Fother?a%253Db%2526c%253Dd - and the server finds itself processing doubly-encoded URL parameters.
I am not really bothered by the fact that slashes get URL-encoded (unlike #2864)
However, I guess my issue is the same as #2863 - I do not think that the % character in my context should be URL encoded.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
Currently, I have an issue that prevents usage of the last version of httpx:
strobject, that I wish to process;strpossible, the query parameters from the URL need to be encoded. However, as slashes are not requiredhave naturally been re-encoded, in which slashes have not been encoded (http://host/path?sub_url=https://other?a%3Db%26c%3Dd);httpxdouble encodes the already existing%characters, sending thehttp://host/path?sub_url=https:%2F%2Fother?a%253Db%2526c%253Dd- and the server finds itself processing doubly-encoded URL parameters.I am not really bothered by the fact that slashes get URL-encoded (unlike #2864)
However, I guess my issue is the same as #2863 - I do not think that the
%character in my context should be URL encoded.Beta Was this translation helpful? Give feedback.
All reactions