Return-Path: 
 <users-return-93483-apmail-httpd-users-archive=httpd.apache.org@httpd.apache.org>
Delivered-To: apmail-httpd-users-archive@www.apache.org
Received: (qmail 66482 invoked from network); 9 Feb 2010 19:32:32 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3)
  by minotaur.apache.org with SMTP; 9 Feb 2010 19:32:32 -0000
Received: (qmail 41566 invoked by uid 500); 9 Feb 2010 19:32:29 -0000
Delivered-To: apmail-httpd-users-archive@httpd.apache.org
Received: (qmail 41514 invoked by uid 500); 9 Feb 2010 19:32:29 -0000
Mailing-List: contact users-help@httpd.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@httpd.apache.org
list-help: <mailto:users-help@httpd.apache.org>
list-unsubscribe: <mailto:users-unsubscribe@httpd.apache.org>
List-Post: <mailto:users@httpd.apache.org>
List-Id: <users.httpd.apache.org>
Delivered-To: mailing list users@httpd.apache.org
Received: (qmail 41504 invoked by uid 99); 9 Feb 2010 19:32:29 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 19:32:29 +0000
X-ASF-Spam-Status: No, hits=2.2 required=10.0
	tests=HTML_MESSAGE,SPF_PASS
X-Spam-Check-By: apache.org
Received-SPF: pass (nike.apache.org: domain of jdveencamp@gmail.com designates
 209.85.218.209 as permitted sender)
Received: from [209.85.218.209] (HELO mail-bw0-f209.google.com)
 (209.85.218.209)
    by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 09 Feb 2010 19:32:20 +0000
Received: by bwz1 with SMTP id 1so818779bwz.12
        for <users@httpd.apache.org>; Tue, 09 Feb 2010 11:32:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=gamma;
        h=domainkey-signature:mime-version:received:date:message-id:subject
         :from:to:content-type;
        bh=BiH5JbTa9yKcMrfjJ53b9ffjxct0xEFyz8juZv2Qa1M=;
        b=YJ6OgO0pBLGQvGnTSO1U9932tpGGYYVTmvodbxzt5tpsUW9vF+uroOtOspQ27YXGO/
         7ZtjAed4gNdXfz5OHY10w5YGH9VlqgSDifpYc4LnISzWBVeXLDLhMmAlWn2K0VfPorRF
         Ms1m0bo3qUdbghCgcCPD+R4N77PdkjAuCka9A=
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=mime-version:date:message-id:subject:from:to:content-type;
        b=XaoKO6PKdW/LwQ5LXSOuSKlnaPiIbG7r9e3heGL1g2Ers/432Xq0RA1/PXFAo6zNBd
         jD0REqfYHtq9iYZnr5NKBVCwUezdHTJgY1OEvl+SaeL5js7W5a2sGODLfuyDA7NEfs8e
         PDjijJlPGbSxSeTK/6XClH5mKHr+xt/zpve6E=
MIME-Version: 1.0
Received: by 10.102.17.4 with SMTP id 4mr5985730muq.4.1265743920212; Tue, 09
	Feb 2010 11:32:00 -0800 (PST)
Date: Tue, 9 Feb 2010 13:31:59 -0600
Message-ID: <24faaf841002091131y352707ccx526f12908243d7fb@mail.gmail.com>
From: Jonathon Veencamp <jdveencamp@gmail.com>
To: users@httpd.apache.org
Content-Type: multipart/alternative; boundary=00163646b9a2bdade3047f2ff8a2
X-Virus-Checked: Checked by ClamAV on apache.org
Subject: [users@httpd] How to force CRLF on non .txt files when directory
 browsing?

--00163646b9a2bdade3047f2ff8a2
Content-Type: text/plain; charset=ISO-8859-1

Hello,

I've beat my head on this wall far too long, and googled the heck out of it,
so I'll ask the mailing list on what should be a simple problem.

I have some text files on a linux host with .log and .properties
extensions.  When these are sent to a windows browser, they do not have
CR/LF and so each line wraps to the next and they don't format well in the
browser.  I would like to have the Apache HTTP server treat these the same
as .txt files, but I've been unable to find the configuration I need to
change.

I tried adding
AddType text/html .log
AddType text/html .properties

and that didn't do it.  Then I tried
AddHandler type-map .log
AddHandler type-map .properties

and that was a no go.

I tried adding these to the mime.types file.

About all I can think of now is to process these files via a CGI script to
output them line by line with a <BR> if necessary, but that seems like
complete overkill.

Can anyone help?

TIA

Jon

--00163646b9a2bdade3047f2ff8a2
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

<div>Hello,</div>
<div>=A0</div>
<div>I&#39;ve beat my head on this wall far too long, and googled the heck =
out of it, so I&#39;ll ask the mailing list on what should be a simple prob=
lem.</div>
<div>=A0</div>
<div>I have some text files on a linux host with .log and .properties exten=
sions.=A0 When these are sent to a windows browser, they do not have CR/LF =
and so each line wraps to the next and they don&#39;t format well in the br=
owser.=A0 I would like to have the Apache HTTP server treat these the same =
as .txt files, but I&#39;ve been unable to find the configuration I need to=
 change.</div>

<div>=A0</div>
<div>I tried adding</div>
<div>AddType text/html .log<br>AddType text/html .properties</div>
<div>=A0</div>
<div>and that didn&#39;t do it.=A0 Then I tried</div>
<div>AddHandler type-map .log<br>AddHandler type-map .properties</div>
<div>=A0</div>
<div>and that was a no go.</div>
<div>=A0</div>
<div>I tried adding these to the mime.types file.</div>
<div>=A0</div>
<div>About all I can think of now is to process these files via a CGI scrip=
t to output them line by line with a &lt;BR&gt; if necessary, but that seem=
s like complete overkill.</div>
<div>=A0</div>
<div>Can anyone help?</div>
<div>=A0</div>
<div>TIA</div>
<div>=A0</div>
<div>Jon</div>

--00163646b9a2bdade3047f2ff8a2--