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
The need arises from having to use the $ character in URL params. But, of course, depending on the use case, this may be necessary for other characters as well.
But, as one might notice, this requires using some internal modules which is not ideal.
Thus, I would propose adding new API that would allow this to be configured by the user. Or integrate it into existing API, such that safe characters can be passed on to percent_encoded from the higher-level API, such as httpx.get
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
-
The need arises from having to use the
$
character in URL params. But, of course, depending on the use case, this may be necessary for other characters as well.For example:
The URL here will be encoded and the
$
will become%24
, but the endpoint expects a literal$
.Currently, my best solution has been to do this:
But, as one might notice, this requires using some internal modules which is not ideal.
Thus, I would propose adding new API that would allow this to be configured by the user. Or integrate it into existing API, such that
safe
characters can be passed on topercent_encoded
from the higher-level API, such ashttpx.get
Beta Was this translation helpful? Give feedback.
All reactions