1.09_02 CGI handler inserts extra newline after headers (from: jesse@fsck.com)

So you know, if you’re wondering why attachments don’t work in 2.1.x

----- Forwarded message from Jesse jesse@fsck.com -----

Return-Path: jesse@fsck.com
Delivered-To: j@pallas.eruditorum.org
Received: by pallas.eruditorum.org (Postfix, from userid 500)
id 8B8E015A89; Thu, 20 Jun 2002 11:16:51 -0400 (EDT)
Resent-From: jesse@pallas.fsck.com
Resent-Date: Thu, 20 Jun 2002 11:16:51 -0400
Resent-Message-ID: 20020620151651.GV7951@pallas.fsck.com
Resent-To: j@fsck.com
Delivered-To: jesse@pallas.eruditorum.org
Received: by pallas.eruditorum.org (Postfix, from userid 500)
id 67BE4119C5; Thu, 20 Jun 2002 02:04:31 -0400 (EDT)Date: Thu, 20 Jun 2002 02:04:31 -0400
From: Jesse jesse@fsck.com
To: mason-devel@lists.sourceforge.net
Cc: autrijus@autrijus.fsck.com
Subject: 1.09_02 CGI handler inserts extra newline after headers
Message-ID: 20020620060431.GU7951@pallas.fsck.com
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.5.1i
X-Spam-Status: No, hits=0.0 required=5.0 tests= version=2.20
X-Spam-Level:

With HTML, this isn’t such a big problem, but when I’m trying to
haul an image or other binary blob out of the database and present
it, man is the client unahppy.

in CGIHandler.pm at right around line 77:

print $r->http_header;

needs to become something like:

my $header = $r->http_header;
chomp $header;
print $header;

Does that sound kosher?

    -j

jesse reed vincent – root@eruditorum.orgjesse@fsck.com
70EBAC90: 2A07 FC22 7DB4 42C1 9D71 0108 41A3 3FB3 70EB AC90

T’waS br|ll1G 4|||> 7#e sl1T#Y T0v3s D1|> gYR3 4nd Gimb@1 1|| 7#E //A83
all |/|1|/|53Y W3R3 d4 60r0GR0V3s @|||> |>4 M0MES wr47H oUTGR4b3.

----- End forwarded message -----

http://www.bestpractical.com/products/rt – Trouble Ticketing. Free.