Hi guys,
Thanks for your replies. Problem still not solved but I'll let
you know if I find an answer.
George.
Lee Goddard wrote:
>
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: MD5
>
> Hi Stas,
>
> On Tuesday, February 4, 2003 at 2:47:43 AM, you wrote:
>
> SB> Lee Goddard wrote:
> SB> [...]
> >> 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.
>
> SB> Apache already fixes up "\n\n" to the right thing. What it really does
> SB> is identifying the Content-type: header, and then adds the terminating
> SB> by itself, because it really sends other headers, before adding an
> SB> empty new line. So it shouldn't matter if you say "\r\n\r\n" or just
> SB> "\n\n", unless there is a bug.
>
> So if Apache (mod_perl) adds this to his script, even
> though it is not a mod_perl script, then shouldn't he
> be calling it from a <Location> that isn't mod_perl
> enabled...?
>
> Sorry, just getting into this Apache module thing....
>
> Cheers
> lee
>
> - --
> Cheers
> Lee mailto:[EMAIL PROTECTED]
>
> $$=qw$808273788400074285838400657879847269820080698276007265677569820727$;
> $$=~s$(\d\d)$\$_.=chr(\$1+32)$ge;eval;
>
> -----BEGIN PGP SIGNATURE-----
> Version: 2.6
>
> iQCVAwUAPj+AYqdrfekeF/QBAQErkgQApGgGWv78D4in/2NmcoBTqMPdKKyYUZia
> ZN7chLUcduSoyqftj70iU0+PCAheJqX6k+9Q/bErraOoP4g3S5aMW99zYMLfXKtx
> XhTHhusNkroSGKpyXI7FlyKOaQqDLN+S8vm5QAlEkZlK6ZfgovgevSnCqfsiuc48
> /EW2drjX1w0=
> =Ef7H
> -----END PGP SIGNATURE-----
--
7, College View, Cirencester, Gloucestershire, GL7 1WD, UK
07957 141204
[EMAIL PROTECTED]
