You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
My own use case has to do with WebDAV. It defines a set of additional HTTP methods including PROPFIND, MKCOL, COPY, MOVE. Also, some REST services employ the PATCH method for modifying a data item in place.
The text was updated successfully, but these errors were encountered:
Hi @sevaa - thanks for your request. It looks like adding support for arbitrary HTTP methods is indeed feasible.
Should we really allow arbitrary HTTP methods, or would it be better / possible / practical to lock down the set of additional methods? Are there any additional considerations I should look into regarding support for WebDAV?
WebDAV defines about 6 additional methods. There is a Microsoft extension that defines about 10 more. I am not currently interested in testing those, but they exist. With this in mind, extending the current radio button based UI doesn't seem practical. Maybe you could introduce a radio button called "Other" with a combo box of additional methods, or with an edit box... Your choice, ultimately.
As for additional considerations, maybe digest auth... WebDAV is rarely anonymous in real life.
My own use case has to do with WebDAV. It defines a set of additional HTTP methods including PROPFIND, MKCOL, COPY, MOVE. Also, some REST services employ the PATCH method for modifying a data item in place.
The text was updated successfully, but these errors were encountered: