CARVIEW

MOTORHOMES

Select Language

HTTP/2 200 content-location: patch.html.gzip vary: negotiate,accept-encoding tcn: choice last-modified: Sat, 12 Jul 2025 08:31:38 GMT etag: "74d-639b7415fa8f3;63605430305ae content-length: 1869 cache-control: max-age=10800 strict-transport-security: max-age=15552000 content-security-policy: default-src 'self'; img-src 'self' data: *.twitter.com *.twimg.com; style-src 'self' *.twitter.com; script-src 'self' *.twitter.com *.twimg.com; frame-src data: *.twitter.com www.youtube.com; frame-ancestors 'none'; report-uri https://mnot.report-uri.com/r/d/csp/enforce link: ; rel=preload;as=font;type=font/woff2;crossorigin=anonymous;nopush, ; rel=preload;as=fetch;crossorigin=anonymous;nopush link: ; rel=preload;as=font;type=font/woff2;crossorigin=anonymous;nopush content-type: text/html; charset=utf-8 content-encoding: gzip content-language: en date: Fri, 10 Oct 2025 12:41:54 GMT server: Apache Go PATCH Go

mark nottingham

Go PATCH Go

Monday, 3 May 2004

HTTP

It looks like the HTTP PATCH method proposal might be based on Delta Encoding, which is IMO one of the cooler and lesser-known HTTP technologies.

I’ve heard of a few implementations of delta, including one by Patrick McManus a long time ago that I believe shows up in Navisite’s DeltaEdge [pdf].

It’s a win-win; less spec work has to be done, implementations can take advantage of existing code if they have it, and it increases the exposure of Delta Encoding, which may solve some other problems people have with HTTP performance.

Original Source | Taken Source

mark nottingham

other HTTP posts

Go PATCH Go