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

Look into how best to represent redirects in WebDAV #24

Open
jwodder opened this issue Jan 29, 2024 · 1 comment
Open

Look into how best to represent redirects in WebDAV #24

jwodder opened this issue Jan 29, 2024 · 1 comment
Labels
correctness Getting it right needs research More information is required WebDAV Specific to the WebDAV protocol/implementation

Comments

@jwodder
Copy link
Member

jwodder commented Jan 29, 2024

  • Aside from the <DAV:reftarget> property in RFC 4437, how should a PROPFIND response best describe a non-collection resource that the server provides as a redirect?

  • Presumably, using the redirected URL as the value of <DAV:href> in responses does not apply here, as the redirected URLs do not support PROPFIND.

  • Is setting <DAV:status> to a 307 response an appropriate way to indicate that the resource is a redirect? When exactly should a 3xx response be used in <DAV:status>?

@jwodder jwodder added correctness Getting it right needs research More information is required WebDAV Specific to the WebDAV protocol/implementation labels Jan 29, 2024
@yarikoptic
Copy link
Member

relates to

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
correctness Getting it right needs research More information is required WebDAV Specific to the WebDAV protocol/implementation
Projects
None yet
Development

No branches or pull requests

2 participants