-
Notifications
You must be signed in to change notification settings - Fork 113
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
Align href url encoding with oc10 #1425
Align href url encoding with oc10 #1425
Conversation
Thanks for opening this pull request! The maintainers of this repository would appreciate it if you would create a changelog item based on your changes. |
1bed621
to
fa19fa6
Compare
@phil-davis how can this
On oc10 the xml of a publicly shared file looks like this: <?xml version="1.0"?>
<d:multistatus
xmlns:d="DAV:"
xmlns:s="http://sabredav.org/ns"
xmlns:oc="http://owncloud.org/ns">
<d:response>
<d:href>/remote.php/dav/public-files/AM3BHmiAWvnxBCX/</d:href>
<d:propstat>
<d:prop>
<oc:permissions></oc:permissions>
<d:resourcetype>
<d:collection/>
</d:resourcetype>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<oc:favorite/>
<oc:fileid/>
<oc:owner-id/>
<oc:owner-display-name/>
<oc:share-types/>
<oc:privatelink/>
<d:getcontentlength/>
<oc:size/>
<d:getlastmodified/>
<d:getetag/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/remote.php/dav/public-files/AM3BHmiAWvnxBCX/ownCloud%20Manual.pdf</d:href>
<d:propstat>
<d:prop>
<oc:permissions></oc:permissions>
<oc:fileid>19</oc:fileid>
<oc:owner-id>admin</oc:owner-id>
<oc:owner-display-name>admin</oc:owner-display-name>
<d:getcontentlength>6662575</d:getcontentlength>
<oc:size>6662575</oc:size>
<d:getlastmodified>Fri, 29 Jan 2021 15:18:49 GMT</d:getlastmodified>
<d:getetag>"e4985b9306b021210b456b88b1a21ad1"</d:getetag>
<d:resourcetype/>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<oc:favorite/>
<oc:share-types/>
<oc:privatelink/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
</d:multistatus> The path expression
on ocis it looks like this: <?xml version="1.0" encoding="utf-8"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:oc="http://owncloud.org/ns">
<d:response>
<d:href>/remote.php/dav/public-files/wCQgXMEmktssxAH/</d:href>
<d:propstat>
<d:prop>
<oc:permissions>S</oc:permissions>
<oc:favorite>0</oc:favorite>
<oc:fileid>MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU3OmU1NzYxZmFiLTYxZjEtNGYyZC04YTI5LWU1NDQ5NTlkZmI5NA==</oc:fileid>
<oc:size>737</oc:size>
<d:getlastmodified>Fri, 29 Jan 2021 15:24:42 +0000</d:getlastmodified>
<d:getetag>"1ba16dcb2464582770a72e52a7297ab7"</d:getetag>
<d:resourcetype>
<d:collection/>
</d:resourcetype>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<oc:owner-id/>
<oc:owner-display-name/>
<oc:share-types/>
<oc:privatelink/>
<d:getcontentlength/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/remote.php/dav/public-files/wCQgXMEmktssxAH/ChatLog%20All%20hands%20call%202021_01_27%2010_03.rtf</d:href>
<d:propstat>
<d:prop>
<oc:permissions>S</oc:permissions>
<oc:favorite>0</oc:favorite>
<oc:fileid>MTI4NGQyMzgtYWE5Mi00MmNlLWJkYzQtMGIwMDAwMDA5MTU3OmU1NzYxZmFiLTYxZjEtNGYyZC04YTI5LWU1NDQ5NTlkZmI5NA==</oc:fileid>
<d:getcontentlength>737</d:getcontentlength>
<oc:size>737</oc:size>
<d:getlastmodified>Fri, 29 Jan 2021 15:24:42 +0000</d:getlastmodified>
<d:getetag>"1ba16dcb2464582770a72e52a7297ab7"</d:getetag>
<d:resourcetype/>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<oc:owner-id/>
<oc:owner-display-name/>
<oc:share-types/>
<oc:privatelink/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
</d:multistatus> which evaluates to
So both return two entries, which makes sense, because webdave requires the parent to be part of the collection of a propfind. Both requests were made against the public-url endpoint:
I did not find any magic that would descend int the dir and do a PROPFIND directly on the file... or that would append the name of the file to the propfind. 🤔 doesnt the test test the wrong entry when used for a file (vs a folder) shared via public link? public function theSizeOfTheFileShouldBe($size) {
$responseXml = HttpRequestHelper::getResponseXml(
$this->response,
__METHOD__
);
$xmlPart = $responseXml->xpath("//d:prop/d:getcontentlength");
$actualSize = (string) $xmlPart[0];
Assert::assertEquals(
$size,
$actualSize,
__METHOD__
. " Expected size of the file was '$size', but got '$actualSize' instead."
);
} |
fa19fa6
to
8846ffe
Compare
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
8846ffe
to
bf6fbc6
Compare
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
bf6fbc6
to
6554e2c
Compare
might be a |
hm the testsuite does not send a depth 0 ... does oc10 default to depth 0? |
no ... bit it does not return any properties as 404 on the root collection of a shared public file: <?xml version="1.0"?>
<d:multistatus xmlns:d="DAV:" xmlns:s="http://sabredav.org/ns" xmlns:oc="http://owncloud.org/ns">
<d:response>
<d:href>/remote.php/dav/public-files/KNghJEjp2XqZI3n/</d:href>
<d:propstat>
<d:prop>
<d:resourcetype>
<d:collection/>
</d:resourcetype>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
</d:response>
<d:response>
<d:href>/remote.php/dav/public-files/KNghJEjp2XqZI3n/ownCloud%20Manual.pdf</d:href>
<d:propstat>
<d:prop>
<d:getlastmodified>Fri, 29 Jan 2021 21:27:32 GMT</d:getlastmodified>
<d:getcontentlength>6662575</d:getcontentlength>
<d:resourcetype/>
<d:getetag>"abc05683012996d0c96249586539a740"</d:getetag>
<d:getcontenttype>application/pdf</d:getcontenttype>
</d:prop>
<d:status>HTTP/1.1 200 OK</d:status>
</d:propstat>
<d:propstat>
<d:prop>
<d:quota-used-bytes/>
<d:quota-available-bytes/>
</d:prop>
<d:status>HTTP/1.1 404 Not Found</d:status>
</d:propstat>
</d:response>
</d:multistatus> |
a5bfc0e
to
08d5c13
Compare
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
08d5c13
to
1acb45e
Compare
@phil-davis I don't know why oc 10 renders the href with different casing. Percent encoding is specified as treating the different caseing of a-f as equivalent: https://tools.ietf.org/html/rfc3986#section-2.1 General URL Handling https://tools.ietf.org/html/rfc4918#section-8.3 Path production rules https://tools.ietf.org/html/rfc3986#section-3.3 Can we make the tests ignore case? I think we should. |
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
Ok so ... Rendering the percent encoded bytes as lowercase seems to work now. I guess I confused the different results at some point... @phil-davis nevermind... I hope ... |
Signed-off-by: Jörn Friedrich Dreyer <[email protected]>
22d4bba
to
6a346fa
Compare
I agree. The core API tests are too strict, because when they were written they were just regression tests for oC10. Now they are being used as "gold" tests against other implementations (OCIS and reva), so they should be given a "correct" amount of flexibility. I raised issue owncloud/core#38367 |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Changes to expected-failures and removal of out-of-date test scenarios LGTM. Someone else can review the actual Golang code here!
Examples: | ||
| dav_version | folder_name | expected_href | | ||
| old | /folder ?2.txt | webdav\/folder%20%3F2\.txt | | ||
| new | /folder ?2.txt | dav\/files\/%username%\/folder%20%3F2\.txt | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to delete these "local" test scenarios. Various core scenarios are now passing, which is great.
Requiring exact values like %3F
is problematic in tests like this - both %3F
and %3f
are valid. I raised issue owncloud/core#38367 to get the core API tests sorted out so that they have the needed flexibility. That way, in future, we can have implementations that return either case and the test suite will allow it.
|
||
// replaceAllStringSubmatchFunc is taken from 'Go: Replace String with Regular Expression Callback' | ||
// see: https://elliotchance.medium.com/go-replace-string-with-regular-expression-callback-f89948bad0bb | ||
func replaceAllStringSubmatchFunc(re *regexp.Regexp, str string, repl func([]string) string) string { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'd like to look into this. Will create an issue
We now use the same percent encoding for URLs in WebDAV href properties as ownCloud 10.
fixes owncloud/ocis#1120
fixes owncloud/ocis#1296
fixes owncloud/ocis#1307
ownCloud 10 relies on sabre/dav to encode the href in xml like this:
https://github.com/sabre-io/http/blob/bb27d1a8c92217b34e778ee09dcf79d9a2936e84/lib/functions.php#L369-L379
I ported the function to go. If anyone wants to go crazy about optimizing it feel free after this PR was merged. I want to make the tests green first.