From: Jason Molenda <jason-gcclist@molenda.com>
To: Gerald Pfeifer <pfeifer@dbai.tuwien.ac.at>
Cc: overseers@gcc.gnu.org, Geoff Keating <geoffk@geoffk.org>,
Janis Johnson <janis187@us.ibm.com>
Subject: Re: Apache handling of .txt.gz
Date: Wed, 05 Feb 2003 18:12:00 -0000 [thread overview]
Message-ID: <20030205101225.A65471@molenda.com> (raw)
In-Reply-To: <Pine.BSF.4.51.0302051729410.90851@naos.dbai.tuwien.ac.at>; from pfeifer@dbai.tuwien.ac.at on Wed, Feb 05, 2003 at 05:31:44PM +0100
On Wed, Feb 05, 2003 at 05:31:44PM +0100, Gerald Pfeifer wrote:
> >
> > I worked around this by putting stuff in a .htaccess file, but thought
> > you should know...
What did you put in the .htacces file?
We run a non-standard module, mod_gzip, on sourceware. If you ask for
index.html and an index.html.gz is also present, and the client browser
claims it can decompres gzip-encoded content, the .gz version is sent.
My initial reaction is to wonder if mod_gzip might be getting involved
somehow.
J
next prev parent reply other threads:[~2003-02-05 18:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20030130181313.7d3c5820.bkoz@redhat.com>
[not found] ` <20030130182059.C23205@synopsys.com>
[not found] ` <jmbs1x877v.fsf@desire.geoffk.org>
[not found] ` <Pine.BSF.4.51.0301312326401.59177@acrux.dbai.tuwien.ac.at>
[not found] ` <200301312245.h0VMjla05130@desire.geoffk.org>
[not found] ` <Pine.BSF.4.51.0302010001350.59177@acrux.dbai.tuwien.ac.at>
[not found] ` <200302040231.h142VPg27860@desire.geoffk.org>
2003-02-05 16:32 ` Gerald Pfeifer
2003-02-05 18:12 ` Jason Molenda [this message]
2003-02-05 18:19 ` Christopher Faylor
2003-02-05 22:05 ` Jason Molenda
2003-02-06 9:59 ` Gerald Pfeifer
2003-02-05 18:27 ` Geoff Keating
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20030205101225.A65471@molenda.com \
--to=jason-gcclist@molenda.com \
--cc=geoffk@geoffk.org \
--cc=janis187@us.ibm.com \
--cc=overseers@gcc.gnu.org \
--cc=pfeifer@dbai.tuwien.ac.at \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).