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

why loss encode for ; in httpurl's QUERY_COMPONENT_ENCODE_SET? #2975

Closed
jiafu1115 opened this Issue Nov 14, 2016 · 4 comments

Comments

2 participants
@jiafu1115

jiafu1115 commented Nov 14, 2016

http://www.freeformatter.com/url-encoder.html

How does URL encoding work?
 
: (Colon) becomes %3A
; (Semi-Colon) becomes %3B

can anybody help to explain it? I use old version's okhttp. it is %3B. but update to newest version, it is still ; with encode. it broken my app.

I doesn't know why to change it?

anybody know it? @swankjesse

@swankjesse

This comment has been minimized.

Show comment
Hide comment
@swankjesse

swankjesse Nov 14, 2016

Member

Consistency with Chrome & Firefox.

Member

swankjesse commented Nov 14, 2016

Consistency with Chrome & Firefox.

@swankjesse swankjesse closed this Nov 14, 2016

@jiafu1115

This comment has been minimized.

Show comment
Hide comment
@jiafu1115

jiafu1115 Nov 14, 2016

@swankjesse How to do if we still want to keep encode to %3B. Or is the server should change to support ; instead of %3B?
Most article mentions it is %3B.

jiafu1115 commented Nov 14, 2016

@swankjesse How to do if we still want to keep encode to %3B. Or is the server should change to support ; instead of %3B?
Most article mentions it is %3B.

@jiafu1115

This comment has been minimized.

Show comment
Hide comment
@jiafu1115

jiafu1115 Nov 14, 2016

@swankjesse if keeping unencode for ; is standard. This need server to support it instead we change?

@swankjesse if keeping unencode for ; is standard. This need server to support it instead we change?

@swankjesse

This comment has been minimized.

Show comment
Hide comment
@swankjesse

swankjesse Nov 14, 2016

Member

Yes.

Member

swankjesse commented Nov 14, 2016

Yes.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment