You are viewing a plain text version of this content. The canonical link for it is here.
Posted to modperl@perl.apache.org by Timon Roth <ti...@digitalforce.ch> on 2012/03/14 08:57:38 UTC
acces control via cookies for webdirectories again
hello list
i habe tried also a second scenario with the
PerlProcessConnectionHandler and the PerlPreConnectionHandler.
i must then first read the header from the client via the socket. thats
very cool. but how can i then route the client forward to the desired
page he initially used wanted to see?
thans for any help and suggestions!
greets,
timon
--
Timon Roth, Triemlistrasse 92, 8047 Zürich
+4143 8174031,+4179 6365728, skype: timon.roth
timon.roth@digitalforce.ch, www.digitalforce.ch
http://tel.search.ch/zuerich/triemlistrasse-92/timon-roth
Re: acces control via cookies for webdirectories again
Posted by Perrin Harkins <pe...@elem.com>.
On Wed, Mar 14, 2012 at 3:57 AM, Timon Roth <ti...@digitalforce.ch> wrote:
> i habe tried also a second scenario with the PerlProcessConnectionHandler
> and the PerlPreConnectionHandler.
>
> i must then first read the header from the client via the socket. thats very
> cool. but how can i then route the client forward to the desired page he
> initially used wanted to see?
Have you looked at Apache::AuthTicket? It provides flexible access
control for directories.
- Perrin
Re: acces control via cookies for webdirectories again
Posted by Rafael Caceres <rc...@aasa.com.pe>.
Timon,
I'd suggest you take a look at Apache2::AuthTicket, and either use it 'as is' or add ad-hoc info to the cookie at creation time. Handler setup would be there and you could also be sure that the id cookie has not been tampered with.
Regards,
Rafael Caceres
----- Original Message -----
From: "Timon Roth" <ti...@digitalforce.ch>
To: "modperl" <mo...@perl.apache.org>
Sent: Wednesday, March 14, 2012 2:57:38 AM
Subject: acces control via cookies for webdirectories again
hello list
i habe tried also a second scenario with the
PerlProcessConnectionHandler and the PerlPreConnectionHandler.
i must then first read the header from the client via the socket. thats
very cool. but how can i then route the client forward to the desired
page he initially used wanted to see?
thans for any help and suggestions!
greets,
timon
--
Timon Roth, Triemlistrasse 92, 8047 Zürich
+4143 8174031,+4179 6365728, skype: timon.roth
timon.roth@digitalforce.ch, www.digitalforce.ch
http://tel.search.ch/zuerich/triemlistrasse-92/timon-roth