At 06:22 PM 1/28/2003, Stas Bekman wrote:
[...]
> Is it true what was said in one of the other
threads -with mod_perl (Apache 1.3.27) the current working directory is
different from the dir where the script lies?
[...]
As I've followed up (because I knew that that particular post will create
At 10:50 AM 1/29/2003, Perrin Harkins wrote:
[EMAIL PROTECTED] wrote:
I'm not sure whether the company that's hosting my web site will want to
install any non-critical module (They ahve done me a favor allowing me to
run mod_perl ... ) So I want to see if I have any options installing it
under
[EMAIL PROTECTED] wrote:
I'm not sure whether the company that's hosting my web site will want to
install any non-critical module (They ahve done me a favor allowing me
to run mod_perl ... ) So I want to see if I have any options installing
it under my directory tree.
Okay. You need to modify
Actually I haven't got this to work. I'm yet trying to figure how to load
the module (PerlModule Apache::SSI) in the .htaccess with it actuall
residing in the "/perl/" directory rather than the standard lib directories.
Why? It's a module, not a CGI script.
I'm not sure whether the company
[EMAIL PROTECTED] wrote:
works with mod_include Got a [an error
occurred while processing this directive] (well actually the errmsg that
I had set) with CGI::SSI. As I said I didn't really follow-up to see if
this is a prob.
Oh, sorry, I missed the part about CGI::SSI. That will work with
At 06:54 PM 1/28/2003, Perrin Harkins wrote:
[EMAIL PROTECTED] wrote:
Tks that way worked except for the #config sizefmt of mod_include
That should work fine. What's broken with it?
(Frankly I'm so eagar to not just get my feet wet in mod_perl (just started
on it today), but drown in it I d
[EMAIL PROTECTED] wrote:
Tks that way worked except for the #config sizefmt of mod_include
That should work fine. What's broken with it?
From the documentation of the Apache::Include I couldn't make out
whether it handled other features like set which I am using.
It does not implement SSI,
[...]
> Is it true what was said in one of the other
threads -with mod_perl (Apache 1.3.27) the current working directory is
different from the dir where the script lies?
[...]
As I've followed up (because I knew that that particular post will create
confusion), it *is* the script's dir for m
You can do this. Technically I think you can POST to a file, but you
don't need to.
You can do this lots of ways, including post-processing the output of a
CGI script with a module like CGI::SSI. What I
Tks that way worked except for the #config sizefmt of mod_include
would suggest is wri