You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
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.
The text was updated successfully, but these errors were encountered: