Thanks for your quick response!
> It's missing in b7, because of the internal changes, but should come in
> again at some point
Great. I would love to get it back... until then, I can live without
it. Its nice to know I'm not blind either...
> > 2. EMBPERL_OBJECT_BASE does not seem to work in my Location pragma
> > - given the config below, I would just get an error in the
> > embperl.log about 'kaka.epl' not being found.
>
> This looks like the EMBPERL_APPNAME isn't set inside the Location block
> (Yes, I see it's there, but maybe it wasn't when you does this test?)
Unfortunately it was there. I just double checked again to be sure.
> > - without the 'root' directive, errormsg changed to '_base.epl'
> > cannot be found.
>
> What do you mean by 'root' diretive?
sorry -- root as in document level, not directive. As *not* in a location,
directory or other 'block'. Sorry about the confusion.
> b7 does for performance reasons not really make a chdir anymore. It still
> handles calls to Execute relative to the diretory of the current script, but
> for external files you have to do it on your own. You can get the current
> directory with
Understandable -- as this is how I found the optDisableChdir -- looking
to turn this function off to increase performance. For functionality
however -- could I suggest that you provide some means to 'enable'
this? I agree it should be off by default, but it could be handy, and
remove a headache or two if you start mixing external and internal
calls...
> > 4. Here is the *real* newbie quesion: Is there an easy way to set options?
> > (aka a readable alternative to the EMBPERL_OPTIONS bitmask)
> > would a start.pl script which each option listed work?
> >
>
> You would be able to use a <Perl> Section and take the Constants from
> Embperl::Constant, but I plan to support clear text names for debug and
> option settings in one of the next releases.
Yet another good idea I would like to cast my vote for.
> > The Indexes thing:
> > Under 2.0b5 I had 'Indexes' turned on so I could go to the dir and run
> > the script I wanted to test. It worked.
> >
> > Under 2.0b7, it stopped working.
>
> Yes, this is still a pending issue. I have to tell Embperl to stop working
> on directories, for now it should be ok to use the EMBPERL_URIMATCH to
> restrict the access to html, epl etc files
All of my tests had the EMBPERL_URIMATCH set to only process .htm? and
.epl files. Ahhh, but that gave me an idea. Yup -- looks like if I
take the EMBPERL_URIMATCH out of the Location block it works.
But it is '403 Forbidden' again if I set
EMBPERL_ALLOW (\.htm.?|\.epl$)
in the 'root' level (ie just in the .conf file, not within a block).
But I can still snag a .txt, which means the ALLOW is working, and the
URIMATCH is as well (the .txt has emmperl code in it for a test).
Review: .txt --> no processing or restriction
.htm? --> processing and restriction via the normal expectations
apache index
control --> adheres to the EMBPERL_URIMATCH, but not EMBPERL_ALLOW
Perhaps that helps.
This still leaves the problem with EMBPERL_APPNAME which is not working
like it should, or some of these variables do not work within such blocks.
Do I need an EMBPERL_APP as well? (the logs show it using Embperl, which
is my guess for what I would set it as)
No mean to harp here, as I think this is great stuff and love the work.
I know that such large changes that are currently being invoked are not easy.
I *do* however have some concerns about this stuff in production, which
I previously didn't. (2.0b5 seemed really stable)
Opinions and recommendations anyone?
2.0b5 seemed to support most of the features I wanted, and is safely in
its 'HTML::' namespace (good timing with that change!!) -- should I
just use that and wait for the newer features to stabilize? Is it more
'beta' than my tests lead me to believe? Should I really consider the
1.3x series?
Vielen Dank fuer ihre Hilfe!!
(thanks for the help)
Cameron
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
