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

URLs to Objects with spaces in the objectname are not rendered correctly #44

Closed
robert-bor opened this Issue Jul 30, 2013 · 2 comments

Comments

Projects
None yet
1 participant
@robert-bor

This comment has been minimized.

Show comment
Hide comment
@robert-bor

robert-bor Jan 19, 2014

Member

The problem is created by a strict interpretation of the HTML specifications:

http://stackoverflow.com/questions/4737841/urlencoder-not-able-to-translate-space-character

The advised solution is to manually convert the plus signs to %20

Member

robert-bor commented Jan 19, 2014

The problem is created by a strict interpretation of the HTML specifications:

http://stackoverflow.com/questions/4737841/urlencoder-not-able-to-translate-space-character

The advised solution is to manually convert the plus signs to %20

@robert-bor

This comment has been minimized.

Show comment
Hide comment
@robert-bor

robert-bor Jan 19, 2014

Member

The most important changes will have to be applied for the TempURL. Note that the objectPath in the plaintext signature will have to be as literal as possible, that is, no URL encoding whatsoever.

Member

robert-bor commented Jan 19, 2014

The most important changes will have to be applied for the TempURL. Note that the objectPath in the plaintext signature will have to be as literal as possible, that is, no URL encoding whatsoever.

robert-bor added a commit that referenced this issue Jan 19, 2014

#44 URL encoding is now always appended with the rule that a plus is …
…replaced by %20. Furthermore the temp URL composition of the plaintext signature is based on the unmodified container and object names, mimicking the composition on the side of Swift.

@robert-bor robert-bor closed this Jan 19, 2014

katta pushed a commit to twxkit/joss that referenced this issue Oct 6, 2014

#44 URL encoding is now always appended with the rule that a plus is …
…replaced by %20. Furthermore the temp URL composition of the plaintext signature is based on the unmodified container and object names, mimicking the composition on the side of Swift.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment