www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Marc Slemko <ma...@znep.com>
Subject Re: protocol/1813: After CGI (POST) HTTP-Headers shown in browser and internal Error "OK" (200) (fwd)
Date Wed, 11 Mar 1998 19:50:00 GMT
The following reply was made to PR protocol/1813; it has been noted by GNATS.

From: Marc Slemko <marcs@znep.com>
To: Apache bugs database <apbugs@apache.org>
Cc:  Subject: Re: protocol/1813: After  CGI (POST) HTTP-Headers shown in    browser and internal
Error "OK" (200) (fwd)
Date: Wed, 11 Mar 1998 12:45:20 -0700 (MST)

   This message is in MIME format.  The first part should be readable text,
   while the remaining parts are likely unreadable without MIME-aware tools.
   Send mail to mime@docserver.cac.washington.edu for more info.
 
 --Multipart_Tue_Feb_17_10:05:22_1998-1
 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
 Content-ID: <Pine.BSF.3.95.980311124517.15492k@alive.znep.com>
 
 
 
 ---------- Forwarded message ----------
 Date: 17 Feb 1998 10:05:22 +0100
 From: Carsten Schabacker <c.schabacker@gis.ibfs.de>
 To: Marc Slemko <marcs@znep.com>
 Subject: Re: protocol/1813: After  CGI (POST) HTTP-Headers shown in    browser and internal
Error "OK" (200)
 
 >>>>> In <Pine.BSF.3.95.980216094021.2516E-100000@alive.znep.com> 
 >>>>>	Marc Slemko <marcs@znep.com> wrote:
 MS> On 16 Feb 1998, Carsten Schabacker wrote:
 
 Hi Marc,
 
 MS> Are you sure it is not a problem with mod_python?
 No, but i can make a try without mod_python ... you are right, the problem
 seems to be in mod_python. 
 
 This is what i found out
 external python:  GET ok   POST ok
 mod_python:       GET ok   POST not ok
 
 (mod_python.c Revision: 4.2 Date: 1998/01/25 10:29:29)
 
 I think i go back to external python.
 
 MS> Is there any authentication required for the document in question?
 Yes, there is a .htaccess file in the directory where the html-pages are 
 stored and in the /cgi-sbin/ directory.
 
 MS> > >Fix:
 MS> I'm not sure I understand what you are saying here...
 As i understand the http protocol there must be a empty newline between the
 headers and the body (like in a e-mail), right ?
 If so: if you put out a empty string followed by a newline the header will
 end and the body starts, this is what i thought what goes wrong.
 
 Thanks for your quick anser,
 		greetings Carsten
 
 --Multipart_Tue_Feb_17_10:05:22_1998-1
 Content-Type: TEXT/PLAIN; CHARSET=US-ASCII
 Content-ID: <Pine.BSF.3.95.980311124517.15492l@alive.znep.com>
 Content-Description: 
 
 GiS - Gesellschaft fuer integrierte Systemplanung mbH   Tel. +49-6201-503-38
 Carsten Schabacker                                      Fax  +49-6201-503-66
 Junkersstr. 2                               E-Mail  c.schabacker@gis.ibfs.de
 D-69469 Weinheim                           private  cs@spock.rhein-neckar.de
 
 --Multipart_Tue_Feb_17_10:05:22_1998-1--

Mime
View raw message