Skip to content

Recognise PATCH as a valid HTTP verb.#1

Closed
bigpresh wants to merge 2 commits into
bestpractical:masterfrom
bigpresh:feature/support-patch-verb
Closed

Recognise PATCH as a valid HTTP verb.#1
bigpresh wants to merge 2 commits into
bestpractical:masterfrom
bigpresh:feature/support-patch-verb

Conversation

@bigpresh

Copy link
Copy Markdown
Contributor

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' }.

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' }`.
(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)
@bigpresh

Copy link
Copy Markdown
Contributor Author

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants