Geek asks and answers

Negotiating / compressing HTTP content: use Base64 with Accept-Encoding / Content-Encoding?

I am wondering if the following idea works against the spirit and / or letter of HTTP Content Negotiation and HTTP Compression .

Situation

An HTTP client requests a resource:

HTTP GET /image.jpeg HTTP/1.1
Accept: image/jpeg

The HTTP server returns this resource:

HTTP/1.1 200 OK
Content-Type: image/jpeg

Idea

The client considers it appropriate to request a resource encoded:

HTTP GET /image.jpeg HTTP/1.1
Accept: image/jpeg
Accept-Encoding: base64

The server executes this request and returns a resource encoded:

HTTP/1.1 200 OK
Content-Type: image/jpeg
Content-Encoding: base64

Question

I am not very happy with this idea. HTTP compression, which uses headers Accept-Encodingand Content-Encoding, is data compression, not an increase in size, as Base64 does.

Is base64it used as a value for these headers as a violation of the spirit and / or letter of the HTTP consignment of content and compression of HTTP content?

+5
1

RFC 2616 3.5 ( ):

       ,     .

" " HTTP.

+6

More articles:


All Articles