-
Notifications
You must be signed in to change notification settings - Fork 187
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
PROPFINDs on single file public link files return incorrect href and downloadURL #4758
Labels
Milestone
Comments
18 tasks
dschmidt
added a commit
to owncloud/web
that referenced
this issue
Oct 7, 2022
Add workaround for owncloud/ocis#4758 Without this workaround we see infinite redirects appending the filename over and over again.
micbar
added
GA-Blocker
Priority:p2-high
Escalation, on top of current planning, release blocker
labels
Oct 7, 2022
dschmidt
added a commit
to owncloud/web
that referenced
this issue
Oct 7, 2022
Add workaround for owncloud/ocis#4758 Without this workaround we see infinite redirects appending the filename over and over again.
kulmann
pushed a commit
to owncloud/web
that referenced
this issue
Oct 10, 2022
Add workaround for owncloud/ocis#4758 Without this workaround we see infinite redirects appending the filename over and over again.
needs a reva update in ocis that pulls in cs3org/reva#3324 |
already pulled in as part of #4781 |
This was referenced Jan 13, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Describe the bug
PROPFINDs to a filename in a single file (!) public link share return invalid
href
anddownloadURL
. The filename seems to be appended to whatever was requested instead of the root of the public link share.Steps to reproduce
PROPFIND
on the file itselfExpected behavior
href
anddownloadURL
point to the canonical correct url of the fileActual behavior
I expect those two requests to return the same
href
anddownloadURL
for the same resource, but as you can see the filename is somehow appended to the requested url.It does not seem to matter what filename is requested, as long as there's a slash and anything after the public link token in the requested url, the filename gets simply appended.
The text was updated successfully, but these errors were encountered: