Received: (qmail 3764 invoked by uid 65534); 25 Feb 2000 23:15:18 -0000
Message-Id: <20000225231518.3762.qmail@locus.apache.org>
Date: 25 Feb 2000 23:15:18 -0000
From: Frank Tegtmeyer <fte@pobox.com>
Reply-To: fte@pobox.com
To: submit@bugz.apache.org
Subject: printenv CGI example doesn't break lines
X-Send-Pr-Version: 3.110

>Number:         5810
>Category:       documentation
>Synopsis:       printenv CGI example doesn't break lines
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    apache
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:
>Class:          change-request
>Submitter-Id:   apache
>Arrival-Date:   Fri Feb 25 15:20:00 PST 2000
>Closed-Date:    Fri Sep 15 13:26:28 PDT 2000
>Last-Modified:  Fri Sep 15 13:26:28 PDT 2000
>Originator:     fte@pobox.com
>Release:        1.3.12
>Organization:
>Environment:
Linux 2.2.14 (SuSE 6.3)
>Description:
The output of the CGI example printenv should contain linebreaks after every variable.
>How-To-Repeat:
http://server/cgi-bin/printenv
>Fix:
change the print line:
print "${var}=\"${val}\"<br>\n";
>Release-Note:
>Audit-Trail:

From: Marc Slemko <marcs@znep.com>
To: Frank Tegtmeyer <fte@pobox.com>
Cc: submit@bugz.apache.org
Subject: Re: documentation/5810: printenv CGI example doesn't break lines
Date: Fri, 25 Feb 2000 16:28:27 -0700 (MST)

 On 25 Feb 2000, Frank Tegtmeyer wrote:
 
 > 
 > >Number:         5810
 > >Category:       documentation
 > >Synopsis:       printenv CGI example doesn't break lines
 > >Confidential:   no
 > >Severity:       non-critical
 > >Priority:       medium
 > >Responsible:    apache
 > >State:          open
 > >Class:          change-request
 > >Submitter-Id:   apache
 > >Arrival-Date:   Fri Feb 25 15:20:00 PST 2000
 > >Closed-Date:
 > >Last-Modified:
 > >Originator:     fte@pobox.com
 > >Release:        1.3.12
 > >Organization:
 > apache
 > >Environment:
 > Linux 2.2.14 (SuSE 6.3)
 > >Description:
 > The output of the CGI example printenv should contain linebreaks after every variable.
 > >How-To-Repeat:
 > http://server/cgi-bin/printenv
 > >Fix:
 > change the print line:
 > print "${var}=\"${val}\"<br>\n";
 
 Erm... hmm?
 
 The script in question outputs text/plain, not text/html, so there is no
 sense adding HTML tags to it...
 

From: Marc Slemko <marcs@znep.com>
To: Apache bugs database <apbugs@apache.org>
Cc:  
Subject: Re: documentation/5810: printenv CGI example doesn't break lines
 (fwd)
Date: Sat, 26 Feb 2000 08:34:48 -0700 (MST)

 ---------- Forwarded message ----------
 Date: Sat, 26 Feb 2000 10:55:14 +0100
 From: Frank Tegtmeyer <fte@pobox.com>
 To: Marc Slemko <marcs@znep.com>
 Cc: Frank Tegtmeyer <fte@fte.to>
 Subject: Re: documentation/5810: printenv CGI example doesn't break lines
 
 On Fri, Feb 25, 2000 at 04:28:27PM -0700, Marc Slemko wrote:
 > On 25 Feb 2000, Frank Tegtmeyer wrote:
 > 
 > > 
 > > >Number:         5810
 > > >Category:       documentation
 > > >Synopsis:       printenv CGI example doesn't break lines
 > > >Confidential:   no
 > > >Severity:       non-critical
 > > >Priority:       medium
 > > >Responsible:    apache
 > > >State:          open
 > > >Class:          change-request
 > > >Submitter-Id:   apache
 > > >Arrival-Date:   Fri Feb 25 15:20:00 PST 2000
 > > >Closed-Date:
 > > >Last-Modified:
 > > >Originator:     fte@pobox.com
 > > >Release:        1.3.12
 > > >Organization:
 > > apache
 > > >Environment:
 > > Linux 2.2.14 (SuSE 6.3)
 > > >Description:
 > > The output of the CGI example printenv should contain linebreaks after every variable.
 > > >How-To-Repeat:
 > > http://server/cgi-bin/printenv
 > > >Fix:
 > > change the print line:
 > > print "${var}=\"${val}\"<br>\n";
 > 
 > Erm... hmm?
 > 
 > The script in question outputs text/plain, not text/html, so there is no
 > sense adding HTML tags to it...
 
 Oops, you are right. Seems to be an error in Opera 3.62beta. It displays
 all lines in one. Please set the status to solved :)
 
 Regards, Frank
 
State-Changed-From-To: open-closed
State-Changed-By: slive
State-Changed-When: Fri Sep 15 13:26:28 PDT 2000
State-Changed-Why:
User error.
>Unformatted:
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]