Well, I didn't see any other replies to this... so I'll comment: I don't get
what you are saying here... Could you rephrase it and clarify if you are
talking about AuthTicket or AuthCookie?
> From: Steven Lembark <[EMAIL PROTECTED]>
> Reply-To: [EMAIL PROTECTED]
> Date: Fri, 07 Dec 2001 01:34:57 -0600
> To: [EMAIL PROTECTED]
> Subject: Problem with Apache::AuthCookie-3.00
>
>
> Getting multiple HTTP replies returned to the client. They
> get a form and followig it an 'access denied' message from
> Apache.
>
> The examples I've seen of login_form code use a simple print to
> get things on the screen (e.g., Apache::AuthTicket).
> I've tried this and various combinations of sending the headers
> and form with no luck.
>
> Ideally Apache::AuthCookie should only require the login_form,
> authen_cred and authen_ses_key sub's to function with the
> addition of login_screen to use a location rather rather than
> #!-ed code for the login form.
>
> Does anyone know of a simple, working example of deriving a
> class from Apache::AuthTicket or some specific documentation
> for a complete class? The code that comes with it is only
> useful for testing; the other modules include quit a bit of
> non-AuthCookie sub's that may have a bearing on how the
> form is handled. The login_form is taken from Apache::AuthTicket
> (basically just a header and static body).
>
> My sub-class also overloads authentication to call login_form($r)
> rather than without arguments.
>
> sub authen_cred( $$\@ ) { "foo" }
>
> sub authen_ses_key( $$$ ) { "foo" }
>
> sub login_form
> {
> my( $class, $request ) = @_;
>
> $request->no_cache( 1 );
> $request->send_http_header( 'text/html' );
> $request->print( $form );
>
> OK
> }
>
>
>
> --
> Steven Lembark 2930 W. Palmer
> Workhorse Computing Chicago, IL 60647
> +1 800 762 1582
>
