Because sending different content based on the content-type the user-agent asks for, e.g. with the "Accept:" header, has explicitly been part of the HTTP spec s

Because sending different content based on the content-type the user-agent asks for, e.g. with the "Accept:" header, has explicitly been part of the HTTP spec since version 1.1 in 1997? https://datatracker.ietf.org/doc/html/rfc2068#section-12 https://datatracker.ietf.org/doc/html/rfc2068#section-12 https://datatracker.ietf.org/doc/html/rfc2068#section-14.1 https://datatracker.ietf.org/doc/html/rfc2068#section-14.1 See also https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_negotiation https://developer.mozilla.org/en-US/docs/Web/HTTP/Content_ne... (FWIW - I don't know if that's how `bzr` does this, but it might, and the concept is 25 years old now.) Edit: s/different content/different representations of the same resource/