Mark Junker

Maybe it might be useful to add a property containing the target state? My assumption was that the context state always contains the target state for all transitioned/initialized events.

@ursenzler No need to hurry, especially if you don't like the breaking changes for 6.0 😉 .

I'm not sure if this is possible, because I couldn't find out whether MKCOL, etc.. are required for WebDAV 1 compliance.

It's for creating a new collection (directory).

I thought a bit about your problem. I guess the following solution would be what you really need: 1. Remove the `OptionsHandler` (service `IOptionsHandler`) 2. Register your own service returning...

It's a performance optimization that went wrong here. Maybe we should use a service to implement checks for those stuff.

That would require one to try to create a file name like `C:\Whatever\stuff.txt`, which might be possible, because `\` isn't recognized as path separator on the ASP.NET Core side. I...

No, not yet. It only implements the standard as defined by the RFCs for WebDAV class 1 and 2.

I'm currently working to get V2 in a publishable state, which includes passing Litmus tests, but my workload is currently extremely high and I am unable to continue working on...

@houbi56 I'm still working on compliance against the WebDAV test suite (https://github.com/tolsen/litmus)