www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Greg Haygood" <greg.hayg...@thinkinc.com>
Subject RE: os-solaris/3298: bad CGI headers due to /etc/resolv.conf
Date Tue, 27 Oct 1998 17:17:55 GMT

i have, and it works fine.  also, i changed the script with

print "content-type: text/plain\n\n"
$|++;

at the start of the script, and

print "bye";
exit(0);

at the end of the perl script, and the error message was printed out after
this message.  nothing weird showed up with the rest of the output.  i also
used telhttp to view the headers coming back from the script, and everything
looked fine.  this error just seems to be leaking out, after processing the
script.

-g


-----Original Message-----
From: coar@apache.org [mailto:coar@apache.org]
Sent: Tuesday, October 27, 1998 10:57 AM
To: apache-bugdb@apache.org; coar@apache.org; greg.haygood@thinkinc.com
Subject: Re: os-solaris/3298: bad CGI headers due to /etc/resolv.conf


[In order for any reply to be added to the PR database, ]
[you need to include <apbugs@Apache.Org> in the Cc line ]
[and leave the subject line UNCHANGED.  This is not done]
[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!         ]


Synopsis: bad CGI headers due to /etc/resolv.conf

State-Changed-From-To: open-feedback
State-Changed-By: coar
State-Changed-When: Tue Oct 27 07:56:43 PST 1998
State-Changed-Why:

Why do you think this is an Apache problem?  The error
message clearly states that the bogus information is
being emitted by the script, so it's the script that's
being affected by the resolver option, not the server.
Try running your script from the command line and see what
output it produces.



Mime
View raw message