fix(http): message anatomy diagram

[bsmth]

Accept can't be a response header, so I'm fixing that.

Actually it can be:

When sent by a server in a response, Accept provides information about which content types are preferred in the content of a subsequent request to the same resource.

Regardless, some improvements to the diagram

Related issues and pull requests:

mdn/content#36029

[pepelsbey]

Looks good :) Thanks. Happy to merge as is, though I wonder what’s the image optimization strategy in shared assets. For example, I noticed unusual ID attribute value in the code and it made me want to optimize this image even more:

<text id="POST / HTTP/1.1 Host: developer.mozilla.org User-Agent: curl/8.6.0 Accept: */* Content-Type: application/json Content-Length: 345 { &#34;data&#34;: &#34;ABC123&#34; }">

[bsmth]

Looks good :) Thanks. Happy to merge as is, though I wonder what’s the image optimization strategy in shared assets. For example, I noticed unusual ID attribute value in the code and it made me want to optimize this image even more:

<text id="POST / HTTP/1.1 Host: developer.mozilla.org User-Agent: curl/8.6.0 Accept: */* Content-Type: application/json Content-Length: 345 { &#34;data&#34;: &#34;ABC123&#34; }">

Good point, I didn't notice that. We should add some configs to this repo so we can compress with svgo (for example) in a consistent way