I agree. Is there a cogent reason why so much stuff is under Apache?
Apache doesn't seem like a proper category. WWW might be better for
web-specific stuff, but for this, it seems like geo is the clear module
directory it should be in:
http://www.cpan.org/modules/by-module/Geo/
Does
I feel like most of my responses on this list ask 'why' rather than
answer a question but:
Assuming you have an internet connection between 1 Mb and 10 Mb
You're internal network is running at 100Mb with 1Gb around the corner
or already going.
Why bother compressing stuff when it seems clear
ME is just windows 98 with some bells and whistles. If you want server,
then win2k Server is still the standard (XP is only for
workstation/desktop).
I think mod_perl/Apache will run fine on ME,2000,XP,and even 98. But
for real server environment, the choice is 2000 Server.
-Original
This seems to be more of a general apache thing. I try never to use the
domain name/IP anywhere that isn't totally necessary. So, instead of:
print redirect(http://a.a.a.a/site/cgi-bin/.cgi;);
Why not:
print redirect(/site/cgi-bin/.cgi);
This way, there is no need to hardcode the
I have three machines, only one of which has the problem:
These do not have the problem:
2.4.18-3smp/Apache 1.3.24/perl 5.6.1/mod_perl 1.26
2.4.7-10smp/Apache 1.3.24/perl 5.6.0/mod_perl 1.26
This one does:
2.4.18-5smp/Apache 2.0.40/perl 5.6.1/mod_perl 1.99_05
All the code is the same. I
I have a script that needs to be run when some one goes to the site:
www.mysite.com/
it seems like the different ways that I've tried simply run the script
through the normal cgi scenario without using perl-handler. Am I
missing something obvious with httpd.conf?
