RE: Betr.: Parameter passing and the authentication framework

2005-10-28 Thread Stewart, Gary

> I think this should be
>  

Doh. Yep; the works a charm. Thanks for that :).

Gary

*
The information contained in this message may be confidential or 
legally privileged and is intended for the addressee only, If you 
have received this message in error or there are any problems, 
please notify the originator immediately. The unauthorised use, 
disclosure, copying or alteration of this message is 
strictly forbidden.
*


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



Betr.: Parameter passing and the authentication framework

2005-10-27 Thread Peter . Urbanus





"Stewart, Gary" <[EMAIL PROTECTED]> wrote on 27-10-2005
10:44:38:

> Hi there,
>
> I'm having some problems with parameter passing (or expression
> matching) and the authentication framework. Basically I have
> something that needs to be authenticated but also needs the request
> parameters available to the match so I have something like
>
> 
>  
>   
>   
>
>

I think this should be
 

>...
>
> or using  would be fine as well. The
> auth-protect handler seems to gobble this up though; is there anyway
> of continuing this data into the rest of the pipe?
>
> Thanks,
>
> Gary
>
> *
> The information contained in this message may be confidential or
> legally privileged and is intended for the addressee only, If you
> have received this message in error or there are any problems,
> please notify the originator immediately. The unauthorised use,
> disclosure, copying or alteration of this message is
> strictly forbidden.
> *
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
Greetings, Peter


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



Parameter passing and the authentication framework

2005-10-27 Thread Stewart, Gary
Hi there,

I'm having some problems with parameter passing (or expression matching) and 
the authentication framework. Basically I have something that needs to be 
authenticated but also needs the request parameters available to the match so I 
have something like


 
  
  
   
   
   ...

or using  would be fine as well. The auth-protect 
handler seems to gobble this up though; is there anyway of continuing this data 
into the rest of the pipe?

Thanks,

Gary

*
The information contained in this message may be confidential or 
legally privileged and is intended for the addressee only, If you 
have received this message in error or there are any problems, 
please notify the originator immediately. The unauthorised use, 
disclosure, copying or alteration of this message is 
strictly forbidden.
*


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