Philip Mak wrote:
In the following situation:
ServerName site1.com
PerlSetVar Global /home/site1/global
PerlRequire site1.pl
ServerName site2.com
PerlSetVar Global /home/site2/global
PerlRequire site2.pl
With the above example httpd.conf, is there a way site1.pl can read
the PerlSetVar Global
Xavier Noria wrote:
On Jan 25, 2004, at 0:05, Stas Bekman wrote:
Ged Haywood wrote:
Hello there,
On Sat, 24 Jan 2004, semuel wrote:
you don't need to "\r\n\r\n". "\n\n" will do the job.
According to the standard you should send both \r and \n.
It is bad practice to play fast and loose with standa
On Jan 25, 2004, at 0:05, Stas Bekman wrote:
Ged Haywood wrote:
Hello there,
On Sat, 24 Jan 2004, semuel wrote:
you don't need to "\r\n\r\n". "\n\n" will do the job.
According to the standard you should send both \r and \n.
It is bad practice to play fast and loose with standards.
http://www.w3.or
In the following situation:
ServerName site1.com
PerlSetVar Global /home/site1/global
PerlRequire site1.pl
ServerName site2.com
PerlSetVar Global /home/site2/global
PerlRequire site2.pl
With the above example httpd.conf, is there a way site1.pl can read
the PerlSetVar Global and see "/home/s
Kee Hinckley wrote:
At 3:01 PM -0800 1/24/04, Stas Bekman wrote:
Kee Hinckley wrote:
DBIx::Recordset relies on the ability to return typeglobs from tied
hashes. This appears to have gone away at some point. Take the
following program below and try it under 5.6 and 5.8.
Kee, please refrain f
At 3:01 PM -0800 1/24/04, Stas Bekman wrote:
Kee Hinckley wrote:
DBIx::Recordset relies on the ability to return typeglobs from tied
hashes. This appears to have gone away at some point. Take the
following program below and try it under 5.6 and 5.8.
Kee, please refrain from asking unrelated to
s> If you want to eliminate the need of the 'print ""' line, you should reverse
s> the order of the commands:
s> local $| = 1; print "Content-type: image/gif\r\n\r\n";
No, that doesn't work - I forget the exact error - something about
"script did not send headers" I think.
Kind Regards,
Chris Dr
Ged Haywood wrote:
Hello there,
On Sat, 24 Jan 2004, semuel wrote:
you don't need to "\r\n\r\n". "\n\n" will do the job.
According to the standard you should send both \r and \n.
It is bad practice to play fast and loose with standards.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html
Not
Kee Hinckley wrote:
DBIx::Recordset relies on the ability to return typeglobs from tied
hashes. This appears to have gone away at some point. Take the
following program below and try it under 5.6 and 5.8.
Kee, please refrain from asking unrelated to modperl questions at the modperl
list. Thank
Matt Sergeant wrote:
On 22 Jan 2004, at 10:02, Ask Solem Hoel wrote:
When I access /perl-status/ on this server i get a 500 Internal Server
Error,
and not much information in the error log but "Undefined subroutine
&Apache::Status::handler called". If I remove the PerlModule
B::TerseSize line f
DBIx::Recordset relies on the ability to return typeglobs from tied
hashes. This appears to have gone away at some point. Take the
following program below and try it under 5.6 and 5.8.
Here is the result under Perl 5.6 (MacOS X Jaguar)
Undefined value
Called fetch(foo)
->
Setting to 1
Hello there,
On Sat, 24 Jan 2004, semuel wrote:
> you don't need to "\r\n\r\n". "\n\n" will do the job.
According to the standard you should send both \r and \n.
It is bad practice to play fast and loose with standards.
http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html
73,
Ged.
--
Repo
Hello There.
If you want to eliminate the need of the 'print ""' line, you should reverse
the order of the commands:
local $| = 1; print "Content-type: image/gif\r\n\r\n";
(That's because the $| is a flashing command. NM)
And you don't need to "\r\n\r\n". "\n\n" will do the job.
Semuel.
-Or
On 22 Jan 2004, at 10:02, Ask Solem Hoel wrote:
When I access /perl-status/ on this server i get a 500 Internal Server
Error,
and not much information in the error log but "Undefined subroutine
&Apache::Status::handler called". If I remove the PerlModule
B::TerseSize line from the apacheconfig,
Hi there,
On Sat, 24 Jan 2004, Chris Drake wrote:
> Reading up on the meaning of "$/" I find that it's on page 666 of
> the perl bible - is this an omen?
Wrong beast. My copy of the Camel Book only goes up to page 645.
> maybe a small extra manual section "EXAMPLES" ...
> (especially for busy
15 matches
Mail list logo
