Support for WebDAV (RFC 4918) Request Methods
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 9.8k
- Forks
- 1.9k
- Avg merge
- 1d 2h
- Merged PRs (30d)
- 41
Description
The reasonable question why it has been implemented as enum ? Feign is a good tool to use for communication with webdav. However webdav uses another official standard(https://tools.ietf.org/html/rfc4918) and requires to pass instead of pre-defined GET, POST etc their owns method names. Is it possible to make it as a String ?
I implemented some hacks to extend the enum via reflection. It works fine with okhttp and does not work with default client (there is the same restriction for method name value). apache http client should work fine as well because org.apache.jackrabbit:jackrabbit-webdav uses it as a basis. Anyway Feign allows us to change http client and use our own however there have been this restriction.
Thank you very much in advance.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing Feign's request-method enum and how the default, OkHttp, and Apache HTTP clients consume method names. Confirm how arbitrary RFC 4918 methods should flow through each client, then add coverage showing custom WebDAV methods are accepted and sent correctly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- api
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100