> I should have said - that's what I'm doing, but it doesn't seem to do the
> trick.
>
> How would epmain.c get hold of this variable?
>
HTML::Embperl::handler retrives it via ScanEnvironment and passes it as
cookie_name parameter to the Execute function. Execute calls SetupConfData,
which creates a C structures which holds all configuration data for that
request, including the cookie_name.
I guess your problem is more a mod_perl problem. Sometimes, I never have
really found out when, mod_perl does set environment variables correct. That
occurs (not always!) if you have for example one var in your main
configuration outside of any container and another var inside a container
(Location/Directory etc.). In this case sometimes, inside the container,
only the var which is set inside the container is visible, but not the one
which is set outside e.g.
PerlSetVar EMBPERL_COOKIE_NAME foo
<Location /bar>
PerlSetVar EMBPERL_OPTIONS 1
</Location>
In this example, somtimes EMBPERL_COOKIE_NAME will not be set inside the
location /bar, also it should. Putting the PerlSetVar EMBPERL_COOKIE_NAME
also inside the Location is the only "solution" I currently know
Gerald
> Mike
>
> ----- Original Message -----
> From: "Krassimir Slavchev" <[EMAIL PROTECTED]>
> To: "Michael Smith" <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
> Sent: Friday, January 12, 2001 12:32 PM
> Subject: Re: EMBPERL_COOKIE_NAME not working quite right?
>
>
> > Use PerlSetEnv EMBPERL_COOKIE_NAME SOME_ID_NAME in httpd.conf
> >
> > Michael Smith wrote:
> >
> > > Dear All, I'm experiencing some weird problems with trying to set
> > > EMBPERL_COOKIE_NAME to something other than EMBPERL_UID. I have had
> > > this working on our production systems for some time, but for some
> > > reason when we've started to use more complicated data structures, it
> > > appears to have come unstuck. Users end up with two different
> > > sessions going on, one keyed by EMBPERL_UID and one by my new cookie
> > > name. I can't quite work out what's going on, but decided to hack
> > > Embperl (1.3.0) to try to fix it. Changing the two occurrences of
> > > EMBPERL_UID in Embperl.pm didn't do the trick, but changing the
> > > occurrence of EMBPERL_UID in epmain.c did. I'm not sure how it all
> > > works, but it seems to me like EMBPERL_COOKIE_NAME might not override
> > > this value on all occasions. Mike
> >
> > --
> > Krassimir Slavchev Bulinfo Ltd.
> > [EMAIL PROTECTED] (+359-2)963-3652
> > http://www.bulinfo.net (+359-2)963-3764
> >
> >
> >
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]