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.

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

Feature #1098: UrlEncodedContent improvement #1099

Conversation

guillaumeblaquiere
Copy link
Contributor

Fixes #1098
Legacy behavior is kept. Tests has been updated.

@guillaumeblaquiere guillaumeblaquiere requested a review from a team as a code owner August 28, 2020 09:05
@google-cla
Copy link

google-cla bot commented Aug 28, 2020

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@google-cla google-cla bot added the cla: no This human has *not* signed the Contributor License Agreement. label Aug 28, 2020
@guillaumeblaquiere guillaumeblaquiere deleted the 1098/uripathencoding branch August 28, 2020 09:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: no This human has *not* signed the Contributor License Agreement.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

UrlEncodedContent class should use URI path encoding
1 participant