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

RestTemplate should not encode fragments (#'s) [SPR-6946] #11611

Closed
spring-projects-issues opened this issue Mar 4, 2010 · 1 comment
Closed
Assignees
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Milestone

Comments

@spring-projects-issues
Copy link
Collaborator

Arjen Poutsma opened SPR-6946 and commented

RestTemplate currently (and wrongly) treats #'s as fragment indicators. Instead, we should consider the # as part of the path or (query).

See RFC 1630:

A reference to a particular part of a document may, including the
fragment identifier, look like

http://www.myu.edu/org/admin/people#andy

in which case the string "#andy" is not sent to the server, but is
retained by the client and used when the whole object had been
retrieved.


Referenced from: commits c91ff13

@spring-projects-issues
Copy link
Collaborator Author

Arjen Poutsma commented

Fixed.

@spring-projects-issues spring-projects-issues added type: enhancement A general enhancement in: web Issues in web modules (web, webmvc, webflux, websocket) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues added this to the 3.0.2 milestone Jan 11, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: web Issues in web modules (web, webmvc, webflux, websocket) type: enhancement A general enhancement
Projects
None yet
Development

No branches or pull requests

2 participants