X-gzip

[Loren Swaggr]

Useof program names for the identification of encoding formats is not desirable and is discouraged for future encodings. Their use here is representative of historical practice, not good design. For compatibility with previous implementations of HTTP, applications SHOULD consider "x-gzip" and "x-compress" to be equivalent to "gzip" and "compress" respectively.

The Content-Encoding representation header lists any encodings that have been applied to the representation (message payload), and in what order. This lets the recipient know how to decode the representation in order to obtain the original payload format. Content encoding is mainly used to compress the message data without losing information about the origin media type.

Note that the original media/content type is specified in the Content-Type header, and that the Content-Encoding applies to the representation, or "coded form", of the data. If the original media is encoded in some way (e.g. a zip file) then this information would not be included in the Content-Encoding header.

Servers are encouraged to compress data as much as possible, and should use content encoding where appropriate. Compressing a compressed media type such as a zip or jpeg may not be appropriate, as this can make the payload larger.

A format using the Lempel-Ziv coding (LZ77), with a 32-bit CRC. This is the original format of the UNIX gzip program. The HTTP/1.1 standard also recommends that the servers supporting this content-encoding should recognize x-gzip as an alias, for compatibility purposes.

A format using the Lempel-Ziv-Welch (LZW) algorithm. The value name was taken from the UNIX compress program, which implemented this algorithm. Like the compress program, which has disappeared from most UNIX distributions, this content-encoding is not used by many browsers today, partly because of a patent issue (it expired in 2003).

\n The Content-Encoding representation header lists any encodings that have been applied to the representation (message payload), and in what order.\n This lets the recipient know how to decode the representation in order to obtain the original payload format.\n Content encoding is mainly used to compress the message data without losing information about the origin media type.\n

Note that the original media/content type is specified in the Content-Type header, and that the Content-Encoding applies to the representation, or \"coded form\", of the data. If the original media is encoded in some way (e.g. a zip file) then this information would not be included in the Content-Encoding header.

\n A format using the Lempel-Ziv coding (LZ77), with a 32-bit CRC.\n This is the original format of the UNIX gzip program.\n The HTTP/1.1 standard also recommends that the servers supporting this content-encoding should recognize x-gzip as an alias, for compatibility purposes.\n

\n A format using the Lempel-Ziv-Welch (LZW) algorithm.\n The value name was taken from the UNIX compress program, which implemented this algorithm.\n Like the compress program, which has disappeared from most UNIX distributions, this content-encoding is not used by many browsers today, partly because of a patent issue (it expired in 2003).\n

I have a question about using the Anaplan integration API V2 guide. Is it possible to upload a csv document inside a .zip file to Anaplan? I'm able to manually upload a zip file with a csv in it, which works, but cannot figure out if its possible to do it with the API. I'm trying to do this with Postman but the data being received in Anaplan is all binary. I'm basically trying to accelerate my uploads via the api using large zipped files. Do I need to post with a certain header? I'm not sure if this is possible or not?

If this is TRUE then you cannot compress the file and load . It defeats the purpose . Uploading a file as single chunk means your file size is small(less than 1 mb) therefore you dont need to compress and you PUT it onto the server by streaming it as an octet stream.

Zip and GZip are different. GZip is a format for compressing a stream of bytes, whereas a Zip file is an archive containing a folder/file structure where the files are compressed using different compression schemes. The API expects gzip-compressed chunk content with Content-Type: application/x-gzip.

Hello, I have a problem with a Caddy version 1.0.3, it is altering the content of my Javascript Files. Doing an analysis with firebug I found that Caddy returns in the Response Header the content-type as application/x-gzip, this is the response header:

Within the gzip handler code there is a comment noting specifically that if the underlying handler does not write a Content-Type, some browsers will assume a content type of application/x-gzip and try to download the file. The gzip handler even attempts to detect the content type (using the Golang http standard library functions) in this event, to try and prevent this.

Hello @Whitestrake, I think you are correct about the underlying handler does not write a Content-Type only for javascript files. See the image attached. I am going to try sending a Content-Type from the application to Caddy and see if this works out.

I want Apache to send static files gzip'ed over the wire, but also want Apache to not always gzip them over and over again. So I thought if it wouldn't be possible to deliver an .gz file if it exists. This set-up:

Actually, this works insofar as the .gz file is sent instead of the .css, if the request goes to /static/style.css. The problem is only, that the file is delivered as "application/x-gzip" and not as "text/css". Using mod_rewrite's T flag doesn't alter this. Neither does an explicit

@Nithya Sorry for the late response! Right now S3 input in Filebeat reads files with bufio.NewReader unless content-type is application/x-gzip, then it uses gzip.NewReader instead. There is no special reader for application/octet-stream yet.

3a8082e126