On Thursday 16 January 2003 19:29, J�rg Walter wrote:
> On Thursday, 16. January 2003 19:07, Kjetil Kjernsmo wrote:
> > Yup. That is, I'll display a login form as a part of most pages,
> > but I'll have a login-page too that displays if people follow a
> > link to a
>
> That small login form would be part of your global design stylesheet.
> it's <form action="X"> parameter should point to your login.xsp.

Yep, that's easy enough. 

> > OK! Yep, here we go, it did set the cookie! :-) Crashed shortly
> > afterwards, though... :-( I had tried to use recognize_user before,
> > I don't know what went wrong then.
>
> Crashed? Segfault?? Or "just" a 500 server error?

Just a 500 :-)

> > Have you looked more at extending SimpleTaglib?
>
> No, not yet. I think I will do so when I merge your patches: I want
> to use them as template.
>
> > I thought about subclassing Auth with my stuff, but I figured I'll
> > wait and see what you come up with... :-)
>
> No, just patch it and send me your patches. Please :-)

Oh, I broke backwards compatibility, when I hacked it... But I'll send 
them to you offlist, anyway, but you probably don't want them as they 
are... 

> > When I count lines (uhm, where did those nice numbers go?), it
> > seems these are lines 52-54...:
> > no strict 'refs';
> > $$session{'auth_access_user'} =
> > $r->pnotes('INPUT')->{'credential_0'}; my $rc;
> >
> > What do you make of it...? I can't see anything going wrong with my
> > $rc, but the line before.... I've not configured in Apache::Request
> > or RequestNotes or anything, but it shouldn't be necessary, should
> > it? Anyway, I'm getting another error (see below), that I should
> > address first.
>
> Now this looks exactly like my last thought. Either $session is
> undefined (which it would be if login.xsp is unprotected) 

Right.

>or
> $r->pnotes('INPUT') is. That would be the case if you're playing with
> subrequests or internal redirects. Your patched version of the
> session plugin, does it still externally redirect to /login.xsp? I
> know someone made a patch to have automatic login pages appear via
> internal redirects.

I'll try to look into that. As I said, I use Mark's patches, so there 
may be something there.

> > Hm, right now, I'm getting
> > [Thu Jan 16 18:24:20 2003] [error] _get_session_from_store: No such
> > file or directory at
> > /usr/local/share/perl/5.6.1/Apache/Session/Lock/File.pm line 62.
>
> Sounds like /tmp/locks doesn't exist, unless you changed
> AxKitSessionDir. This is a good sign, however, since this means it
> now tries to allocate a session record. I guess we are not far from
> it now.

Great! I didn't change AxKitSessionDir, though I tried to figure out 
something to set to point it at /var/lock. /tmp/locks did indeed not  
exist, but creating it (and setting uid and gid to www-data) didn't 
help... Uhm, now I see, it's /tmp/sessions/locks ! :-) 

Mmmmm, cookies! :-) It threw me a bunch of cookies before stopping with 
[Thu Jan 16 19:58:42 2003] [warn] [client 195.1.208.96] [AxKit] Caught 
an exception
[Thu Jan 16 19:58:42 2003] [warn] [client 195.1.208.96] [AxKit] aborting 
with code 500
But that's an unprotected /login.xsp.


> > [Thu Jan 16 18:55:57 2003] [crit] [client 195.1.208.96]
> > configuration error:  couldn't check user.  No user file?:
> > /login.xsp
> >
> > This is weird, because it seems that it falls back to Basic
> > authentication, but that's rather meaningless, I would think...
> > I've
>
> Some typo?

I'll stare.... :-) I really can't see any, but I'll stare some more...

> > seen those before too, they seem to crop up when I'm accessing
> > something protected... I've tried to include
> >     PerlFixupHandler Apache::AxKit::Plugin::Session->recognize_user
>
> No, only use either this one or the other two, you never need both.

Good! 

Cheers,

Kjetil
-- 
Kjetil Kjernsmo
Astrophysicist/IT Consultant/Skeptic/Ski-orienteer/Orienteer/Mountaineer
[EMAIL PROTECTED]  [EMAIL PROTECTED]  [EMAIL PROTECTED]
Homepage: http://www.kjetil.kjernsmo.net/


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to