I had no clue either, but using the Apache Cookie module instead fixed it.
Arnold
On Mon, 29 May 2000, Kenneth Lee wrote:
> I see this line in my error_log,
>
> (offline mode: enter name=value pairs on standard input)
>
> And I sure it is caused by CGI::Cookie->parse (or fetch).
> Any id
Hi
I thought Reload would be quite helpfull because of not having to restart
the server, but now I am quite stuck. Only the first form shows all the
changes immediately. The second form after pushing a button does not.
Is this explainable?
Arnold
perl.conf starting:
PerlRequire
Hi
I am using the CGI table function to print tables;
These tables can become quite large.
The html result is generated in a single print.
So using $| to show some output to the user is not of any use since it
works after every print..
I find the table function convenient, so I was hoping for
On Tue, 12 Sep 2000, Pramod Sokke wrote:
> Hi all,
>
> Are there any benchmarking utilities/guidelines that I can use to prove the
>performance boost with mod_perl? We just moved all our old cgis to work under
>mod_perl.
> I'm using Solaris 2.7/Apache 1.3.12/mod_perl 1.24.
> Thanks,
> Pramod
---
> #!/usr/bin/perl -w
>
> use CGI qw/:standard/;
> use CGI::Carp 'fatalsToBrowser';
> use DBI;
> use strict;
>
> my $query= new CGI;
> my $dsn="DBI:mysql:database=authuser;host=localhost;port=3306";
> my $loginname="test";
On 14 Sep 2000, Joe Schaefer wrote:
> Stas,
>
>
> http://perl.apache.org/guide/scenario.html#Buffering_Feature
> ...
> There is no buffering of data uploaded from the client browser to the proxy,
> thus you cannot use this technique to prevent the heavy mod_perl server from
> being tied up
Hi
type: multipart/x-mixed-replace
use CGI::Push qw(:standard)
do_push(-next_page=>\&draw_a_page)
sub draw_a_page {
my ($q,$counter)= @_;
return undef if $counter >100;
my $time = localtime();
return start)html(),
Hi
I know that one is supposed to use a plain httpd or possibly thttpd
for delivering static content like images.
That is however a problem if the images itself are subject to protection.
One option is basic atuhentication, but than the user/password goes to the
server for every image to G
This code does not work under modperl
though tested as a small commandline script it does work.
Also when I change the m6 to a number(ie primary recordkey) it will work
Very strange Although I work around this by using the numbers, I feel a
bit limited by using numbers only..
Maybe the bogus D
Hi
I am using a cookie based authentication scheme.
Cookie expires therefore login again. ( like the ticket master example in
O'reilly's.)
I noticed that the MS Explorer remembers both username and corresponding
password, making the cookie based authentication system useless.
(closing and r
I once used this:
Is PerlCleanupHandler the same as LogHandler?
As far as I remember putting the code in the cleanup phase would mean
logging after finishing the request cycle with no delay for the client.
Is that true?
SetHandler perl-script
PerlHandler Bankers::
Similar problem here but not quite
First time now I want to use a database handler more persistent.
Not yet by using Apache::DBI but in a global $DBH
Shouldn't this just work?
I did not put Apache::DBI in startup file
I also tried code outside handler and I tried server restarts.
I always
I read th FAQ but no succes:
kampen@eureka:/w20/htdocs/xmltest > strings /w20/bin/httpd |grep -i XML
kampen@eureka:/w20/htdocs/xmltest >
I removed ssl and php4 from the build and only concentrated on modperl
1.26 and apache 1.3.20:
[Sun Sep 30 18:06:32 2001] [notice] Apache/1.3.20 (Unix
I used the an test.xml from example taken from axkit.org
Installed most components
kampen@eureka:~/down/cpan/AxKit-1.4 > perl Makefile.PL
checking for module mod_perl >= version 1.17... yes
checking for module XML::Parser >= version 2.27... yes
checking for module Digest::MD5 >= ver
The Nimda worm deposits many files, some of which are hidden in different
directories on the infected server. The worm plants itself in the root of
any available drive as the file admin.dll. Other filenames for the worm
include: ADMIN.DLL, LOAD.EXE, MMC.EXE, README.EXE, RICHED20.DLL,
MEP*.TM
15 matches
Mail list logo
