Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

In order to compatible with more scenarios，can we be customize the parameter SAFEQUERYSTRINGCHARS_URLENCODER? #1780

Open
yzmkbk opened this issue Nov 10, 2022 · 0 comments
Open

In order to compatible with more scenarios，can we be customize the parameter SAFEQUERYSTRINGCHARS_URLENCODER? #1780

yzmkbk opened this issue Nov 10, 2022 · 0 comments
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.

Comments

@yzmkbk
Copy link

yzmkbk commented Nov 10, 2022

SAFEQUERYSTRINGCHARS_URLENCODER: A string of characters that do not need to be encoded when used in URI query strings, as specified in RFC 3986. Note that some of these characters do need to be escaped when used in other parts of the URI.

when the server framework complies with old and new W3C specifications which are different. When the request contains "; ", Google-http-java-client does not escape it, but the server does.

In order to compatible with more scenarios，can we be customize the parameter SAFEQUERYSTRINGCHARS_URLENCODER?
@ldetmer ldetmer added the type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design. label Feb 12, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
type: feature request ‘Nice-to-have’ improvement, new feature or different behavior or design.
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@ldetmer @yzmkbk