-form-urlencode). I can do that with cURL, but to do it with
Apache::Test ?
Thanks,
Jean-Michel
-form-urlencode). I can do that with cURL, but to do it with
Apache::Test ?
Thanks,
Jean-Michel
Gossamer-Threads has a pretty cool mod_perl setup. You can get a
dedicated server or a shared account. Each shared account has its own
apache process, which means that you can log in and control (i.e. stop /
start / restart) your own modperl httpd.
All the mod_perl processes are behind a small,
connections but that doesn't happen for HEAD requests - only for GETs.
Hence there should be no ill side effects by stripping the
Content-Length metadata for HEAD requests.
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/m
e credit card again since the state has become 'accepted'.
This way you don't need to break standard browser functionality...
Does this make sense?
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
Lis
ant to
break such a basic, important piece of standard functionality.
http://www.google.com/search?q=usability+back+button
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apach
assuming you don't want to use basic or digest http authentication (aka
popup boxes, which manage this kind of thing for you) typically the second
(and future) script is kept unaware of the username/password. instead, the
authentication script verifies the user/password and generates some kind of
edily.
There are already programs that do that, so you don't need to write
anything, merely looking in sourceforge and freshmeat or googling for
'imap proxy'.
Of course if you like self-inflicted pain you could write your own proxy
daemon using Perl and Mail::IMAPClient.
Cheers,
://search.cpan.org/search?query=apache+session
Also if you want to keep stuff in memory that is shared between
processes, memcached should do the trick quite neatly.
http://search.cpan.org/~bradfitz/Cache-Memcached/Memcached.pm
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail
er library such as CGI.pm?
Cheers,
--
Jean-Michel Hiver - MKDoc Ltd
http://mkdoc.com/
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
I S wrote:
Thanks. Yet, the web site and practical mod_perl book says that "
"|Can't load DBI|" or *similar error for the IO module or whatever
dynamic module mod_perl tries to pull in first*. The solution is to
re-configure, re-build and re-install Perl and dynamic modules with the
followi
Problem: Can't load ' ../auto/DBI/DBI.so for module
DBI.
Well, you could try Net::MySQL instead which is pure perl.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Perrin Harkins wrote:
On Mon, 2004-03-15 at 16:23, Jean-Michel Hiver wrote:
Yes, what I'm trying to achieve is get Apache::Registry to send custom
404 pages - just like under mod_cgi.
I assume that means you want to be able to run the exact same script
under mod_cgi? And you don&#
old
'use', i.e.
use Apache::DBI;
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
Perrin Harkins wrote:
On Mon, 2004-03-15 at 16:23, Jean-Michel Hiver wrote:
Yes, what I'm trying to achieve is get Apache::Registry to send custom
404 pages - just like under mod_cgi.
I assume that means you want to be able to run the exact same script
under mod_cgi?
Well
ou're
trying to accomplish, maybe we can suggest a better way.
Hi Perrin,
Yes, what I'm trying to achieve is get Apache::Registry to send custom
404 pages - just like under mod_cgi.
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http:/
I don't think this is ever going to work in mp1 under Registry. for the
most part, allowing a script to set the status of the response line is a
hack - I'm not sure how widely documented it is (I've only ever seen it in
comments in Apache core myself) and I don't see the code at all in Apache
2.0
ich containing just one space character.
Hope this helps.
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
script PLUS
* Apache's default ErrorDocument
Under mod_cgi, Apache sends only the first two elements of the above list.
Does it sound familiar?
Any ideas?
Cheers,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiq
Once you run the above at the very beginning of your script, it'll
pull out $r out from thin air from that point on. that's exactly what
+GlobalRequest does.
True, but since it is not necessary to do this first operation with mp1,
when you use Apache::compat with mp2 this should be done for yo
andler are supposed to use
the mod_perl API where ModPerl::Registry scripts aren't. Although it
would be nice to have the option to populate %ENV twice: once before the
first Perl*Handler and once before the response phase.
Thanks,
Jean-Michel.
--
Report problems: http://perl.apache.org
PerlInitHandlers.
When there is no PerlInitHandler, the ENV variable PATH_INFO is around
as usual.
However, when there is a PerlInitHandler, then the PATH_INFO vanishes
and is replaced by SCRIPT_NAME!
Any ideas of what might be going on?
Cheers,
Jean-Michel.
--
Report problems: http
very good plan indeed :)
Best Regards,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
much interested in this alternative so I'll stop here :-)
Best Regards,
Jean-Michel.
--
Report problems: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
List etiquette: http://perl.apache.org/maillist/email-etiquette.html
a whole lot of commerce stuff.
Authentication can be done using HTTP authentication without using
cookies or URI session tracking (which is, frankly, very ugly).
Cheers,
--
Building a better web - http://www.mkdoc.com/
-----
Jean-Michel Hiver
[EMAIL PRO
executed?
Any other ideas?
Cheers,
[1] http://search.cpan.org/~jhiver/MKDoc-Apache_Cache/lib/MKDoc/Apache_Cache.pm
--
Building a better web - http://www.mkdoc.com/
-
Jean-Michel Hiver
[EMAIL PROTECTED] - +44 (0)114 255 8097
Homepage: http
Speedup Apache::Registry scripts!
Not so long ago I was enquiring the mod_perl list on how to capture
Apache::RegistryNG's output by subclassing it. Thanks to the list help,
here is this new module.
MKDoc::Apache_Cache is a drop-in replacement for Apache::Registry. It
uses Cache::FileCache as a c
> Nope. That's a very bad idea. I don't want to go and rewrite all my code to
> use Apache2::Request and dozens of other modules, which work exactly the same
> as before, but their guts are different.
I would tend to agree with Jay though: I would consider Apache and
Apache2 are two different pr
three httpd processes running
concurrently with each different states.
Using httpd -X often helps tracking down where the problem lies since it
starts only one apache process.
Cheers,
--
Building a better web - http://www.mkdoc.com/
-----
Jean-Michel Hiver
[EMA
a list of all your global variables
and localize them in your main cgi script:
local $SomePackage::SomeVariable = undef;
local %OtherPackage::SomeHash= ();
etc.
And see how it goes.
Cheers,
--
Building a better web - http://www.mkdoc.com/
-----
Je
ble, useful, and release on
CPAN I guess...
Cheers,
--
Building a better web - http://www.mkdoc.com/
-----
Jean-Michel Hiver
[EMAIL PROTECTED] - +44 (0)114 255 8097
Homepage: http://www.webmatrix.net/
--
Reporting bugs: http://perl.apache.org/bugs/
Mail li
ry to Apache::CachedRegistry or something...
Cheers,
--
Building a better web - http://www.mkdoc.com/
-
Jean-Michel Hiver
[EMAIL PROTECTED] - +44 (0)114 255 8097
Homepage: http://www.webmatrix.net/
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
d_perl gurus spirits when I'm super-stuck,
which unfortunately is the case right now :(
Cheers,
--
Building a better web - http://www.mkdoc.com/
-
Jean-Michel Hiver
[EMAIL PROTECTED] - +44 (0)114 255 8097
Homepage: http://www.webmatrix.net/
--
Reporting bugs: http://perl.apache.org/bugs/
Mail list info: http://perl.apache.org/maillist/modperl.html
n the output of Apache::RegistryNG and writes
it into '/tmp/foo'. (Attached file).
However, I cannot get this same module to actually send correctly the captured
output... Have you got any suggestions?
Thanks a bunch,
--
Building a better web - http://www.mkdoc.com/
---
you take in order to write one? I've
contemplated the idea but I'm stuck with capturing Apache::Registry or
Apache::RegistryNG's output.
Cheers,
--
Building a better web - http://www.mkdoc.com/
---------
Jean-Michel Hiver
[EMAIL PROTECTED] - +44
35 matches
Mail list logo
