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

PATCH methods #36

Closed
whoshuu opened this issue Sep 1, 2015 · 0 comments
Closed

PATCH methods #36

whoshuu opened this issue Sep 1, 2015 · 0 comments

Comments

@whoshuu
Copy link
Contributor

whoshuu commented Sep 1, 2015

As per RFC 5789. Mechanically, the data being sent up should be similar to what's being done for a PUT, even if the semantics are all not the same (PUT's are usually for whole object replacements, PATCH's are usually for partial updates to existing objects).

The curl option to set is this:

curl_easy_setopt(curl_handle, CURLOPT_CUSTOMREQUEST, "PATCH");

The documentation can probably be folded into the header PUT Requests under a more inclusive name. Testing is a bit more involved, but can be done after the main implementation and documentation, which should be easy.

@whoshuu whoshuu added this to the 1.2 milestone Sep 1, 2015
whoshuu added a commit that referenced this issue Oct 29, 2015
whoshuu added a commit that referenced this issue Oct 29, 2015
whoshuu added a commit that referenced this issue Oct 29, 2015
whoshuu added a commit that referenced this issue Oct 29, 2015
References #36
whoshuu added a commit that referenced this issue Oct 29, 2015
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

1 participant