Is there any way to disable or bypass SavedRequestAwareWrapper?
I have run into bug SEC-363, and I need the quickest possible workaround.
I'm wondering if it's possible to just turn off saving the request and
either (1) always redirect to the home page, or (2) pass in the desired
redirect URL as
I added a test case to SEC-363 to reproduce the bug using the contacts
filter sample. Will someone please reopen it? Thanks.
On 2/20/07, Jeoff Wilks [EMAIL PROTECTED] wrote:
Is there any way to disable or bypass SavedRequestAwareWrapper?
I have run into bug SEC-363, and I need the quickest
Ben, can you elaborate a bit on how you structured your DB schema for ACLs? I'm facing this problem right now (need ACLs at both app
level and database level), and I would appreciate understanding a little more
about the intent of the Acegi design in that respect. (Apologies for resurrecting an
Could you do a similar thing to support both Basic Auth and Form-Based Auth?I need to be able to accept Basic Auth from programmatic/machine clients (python, curl, etc.) but show Form Auth to human users.It's not immediately obvious to me how you'd do this, since Basic Auth normally prompts with a
