-----BEGIN PGP SIGNED MESSAGE-----
Hash: MD5
Hi George,
On Monday, February 3, 2003 at 10:47:47 PM, you wrote:
GS> Hi Lee,
GS> Thanks for your reply. I tried the script you sent and it failed
GS> with "document contains no data". This is odd because I
GS> previously found that mod_perl API scripts ran ok but CGI scripts
GS> running under mod_perl failed.
GS> The script printed some output in the log which I have attached
GS> below. I've also attached the earlier messages in the thread in
GS> case they might help.
Yes, sorry: it sent the warnings to the log.
I just meant that if you ran that little script
from the command line, it should show you exactly
what you are getting back: whether or not the
document really has no data, or whether there is
a CRLF missing between the header and content body.
My guess is that it's your user agent, not your
server. I've had all sorts of problems with Macintosh
browsers not displaying things that everything except
Lynx will.....
I don't know: you're doing this:
print "Content-type: text/plain\n\n";
print "Hello World\n";
Does it (probably not) make any difference if
you do a full CRLF, as perldoc perlop:
For example, most networking protocols expect
and prefer a CR+LF (""\015\012"" or ""\cM\cJ"") for line terminators,
and although they often accept just ""\012"", they seldom tolerate just
""\015"". If you get in the habit of using ""\n"" for networking, you
may be burned some day.
- --
Cheers
Lee mailto:[EMAIL PROTECTED]
$$=qw$808273788400074285838400657879847269820080698276007265677569820727$;
$$=~s$(\d\d)$\$_.=chr(\$1+32)$ge;eval;
-----BEGIN PGP SIGNATURE-----
Version: 2.6
iQCVAwUAPj7mfqdrfekeF/QBAQHcogP+P6ebE/Qz72C6s960eRTG7v18IMBW3y1U
e0QD4gjmlrDKwXhUKSfQYj3PEE0RJ06E/XeyqkGa08wnHWmMvAURuIDsiffaSIbl
pmWBEWMwoJBy0ywXPa4vMVRH/FvII7nGdymCkFSW5bzwRi2TxTxnIogZScMaB1Kd
5GFV7Wpgsj8=
=MQdQ
-----END PGP SIGNATURE-----
