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

Interoperability failure with SAP due to URI encoding #9226

Closed
cyberduck opened this issue Jan 21, 2016 · 2 comments
Closed

Interoperability failure with SAP due to URI encoding #9226

cyberduck opened this issue Jan 21, 2016 · 2 comments
Assignees
Labels
bug thirdparty webdav

Comments

@cyberduck
Copy link
Collaborator

@cyberduck cyberduck commented Jan 21, 2016

74e1f1f created the issue

SAP offers WEBDAV access to it's servers but the URLs are a bit special. They include brackets "(" and "=" as in the following example:
http://mysapserver/sap(Yz0wMDEmbD1lbg==)/bc/bsp_dev/sap/decode_url

Unfortunately, Cyberduck encodes such URLs as:
http://mysapserver/sap%28Yz0wMDEmbD1lbg%3D%3D%29/bc/bsp_dev/sap/decode_url/

Which results in WEBDAV failing as SAP does not expect/support this.

We have verified it in Fiddler by changing the Cyberduck request and when the brackets are included unencoded everything works fine.

I guess one could debate the RFC* but it would be nice to include an option that Cyberduck does not encode such characters in URLs.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 21, 2016

@dkocher commented

Parantheses and equal sign are part of the reserved characters as defined in Uniform Resource Identifier (URI): Generic Syntax. There is no ambiguity here. For reference also refer to Percent-encoding.

Please report a bug with the product vendor referencing this ticket.

@cyberduck
Copy link
Collaborator Author

@cyberduck cyberduck commented Jan 21, 2016

74e1f1f commented

I would like to question your assumption that special characters must always be percent encoded. According to your link and the RFC:

"When a character from the reserved set (a "reserved character") has special meaning (a "reserved purpose") in a certain context, and a URI scheme says that it is necessary to use that character for some other purpose, then the character must be percent-encoded."

Assuming SAP is using the brackets for their intended "reserved purpose" then the client should not be encoding them.

@iterate-ch iterate-ch locked as resolved and limited conversation to collaborators Nov 26, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
bug thirdparty webdav
Projects
None yet
Development

No branches or pull requests

2 participants