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

https://datatracker.ietf.org/doc/html/rfc4918 instead of https://datatracker.ietf.org/doc/html/rfc2518 #64

Open
maulik-modi opened this issue Nov 2, 2021 · 3 comments

Comments

@maulik-modi
Copy link

Implement https://datatracker.ietf.org/doc/html/rfc4918 instead of RFC2518

@ramondeklein
Copy link
Owner

Wish I knew of that one before, so I could have implemented it directly. Could you explain why you need RFC4918, so I can prioritize? I haven't had much time lately to work on NWebDAV and probably won't in the next few months. A PR would be very welcome.

@maulik-modi
Copy link
Author

It is just that RFS2518 is obsolete. For new comers, RFC4918 should be the way to go.

@hnnweb
Copy link

hnnweb commented Oct 28, 2022

it would be great with RFC4918 support as we are trying to implement WebDav for Word support using the Office URI scheme:
https://learn.microsoft.com/en-us/office/client-developer/office-uri-schemes?redirectedfrom=MSDN.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants