> From: Robert Thompson <[EMAIL PROTECTED]>
> > From: Philip Newton [mailto:[EMAIL PROTECTED]]
> > At a guess: "Content-Encoding: gzip" instead.
> Yep that worked,
According to RFC2616 Content-Encoding: x-gzip should have worked as well:
Use of program names for the identification of encodin
Robert Thompson wrote:
> > > I've had a look at the relevant rfc's.
> >
> > Which ones? RFC 2616 (HTTP/1.1) mentions "gzip" not "x-gzip"
> > under "3.5 Content Codings" and "3.6 Transfer Codings".
>
> I was looking at RFC's 2045 & 2046 which relate directly to
> MIME.
Ah, well: Multipurpose I
> From: Philip Newton [mailto:[EMAIL PROTECTED]]
> At a guess: "Content-Encoding: gzip" instead.
Yep that worked,
thanks
Rob
-
I must memorise rfc's
I must memorise rfc's
I must memorise rfc's
---
> From: Philip Newton [mailto:[EMAIL PROTECTED]]
>
> At a guess: "Content-Encoding: gzip" instead.
Thanks, I'll give that a try.
> > I've had a look at the relevant rfc's.
>
> Which ones? RFC 2616 (HTTP/1.1) mentions "gzip" not "x-gzip"
> under "3.5
> Content Codings" and "3.6 Transfer Co
Robert Thompson wrote:
> print "Content-Type: application/octet-stream\n";
> print "Content-Transfer-Encoding: x-gzip\n\n";
At a guess: "Content-Encoding: gzip" instead.
> I've had a look at the relevant rfc's.
Which ones? RFC 2616 (HTTP/1.1) mentions "gzip" not "x-gzip" under "3.5
Content Codi
