Mark Junker

@julienGrd Yes, definitely

Sorry, I'm not really sure what you mean. There are either exceptions handled by ASP.NET Core itself and those handled by the custom `IExceptionFilter` implementation (`WebDavExceptionFilter`), which handles the following...

What kind of exception do you get?

Aha, so it's an `IOException`, that was the missing piece. Then I suggest that you implement and register your own `IExceptionFilter` and return the correct HTTP status code and the...

The changes you made are also available in the release/2.0 branch, but I used an ExceptionFilterAttribute instead of the IExceptionFilter. I'll leave this ticket open, because maybe we need to...

This server doesn't support microsoft specific extensions, but you have two extension points: 1. `IEntryPropertyInitializer` (singleton, default implementation `DefaultEntryPropertyInitializer`) which is used to initialize the default (and maybe custom) properties...

Maybe you can try to implement a request filter that forbids `PROPFIND` on a collection?

Regarding internal APIs: Microsoft uses special "ref" assemblies (e.g. for [Microsoft.Extensions.Configuration.Abstractions](https://github.com/dotnet/runtime/tree/main/src/libraries/Microsoft.Extensions.Configuration.Abstractions/ref)). This allows a very fine control regarding the API to be exposed. EDIT: This also means that you can...

The support of CHUNKING without BINARYMIME is also explained in the Postfix documentation: https://www.postfix.org/BDAT_README.html

You're right, that the dependency on NGettext isn't really needed. I used it to support gettext-style translation support out of the box, but it seems that it's currently not useful/necessary...