Recognise PATCH as a valid HTTP verb. #1

Closed
wants to merge 2 commits into
from

Projects

None yet

2 participants

@bigpresh

This is defined in RFC5789: http://tools.ietf.org/html/rfc5789

This is in active use by GitHub's v3 API, among others.

As a quick overview for anyone unfamilar with PATCH, it's basically a
partial-PUT, passing only the changes - for instance, let's say you wanted to
update a customer's contact email address, you might send a PATCH request to
/customer/42/contactdetails with a JSON payload describing just the parts
which have changed, for instance { email: 'bob@example.com' }.

bigpresh added some commits Oct 17, 2011
@bigpresh bigpresh Recognise PATCH as a valid HTTP verb.
This is defined in RFC5789: http://tools.ietf.org/html/rfc5789

This is in active use by GitHub's v3 API, among others.

As a quick overview for anyone unfamilar with PATCH, it's basically a
partial-PUT, passing only the changes - for instance, let's say you wanted to
update a customer's contact email address, you might send a PATCH request to
`/customer/42/contactdetails` with a JSON payload describing just the parts
which have changed, for instance `{ email: 'bob@example.com' }`.
f7382f2
@bigpresh bigpresh Gah - unbreak it!
(Sorry - just have used $ to jump to EOL in insert mode by mistake or something,
and didn't notice.  Despite it being  a simple change, I should have tested it
before submitting the PR.  /me hangs head)
d68c956
@obra
Best Practical Solutions member

Would you mind rebasing, so we just have one clean commit to merge?

@bigpresh

Sure - closing this PR, and replacing it with one with a single commit.

@bigpresh bigpresh closed this Nov 28, 2011
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment