Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail From: Robert Klemme Newsgroups: comp.lang.java.programmer Subject: Re: Browser Back Button Date: Wed, 11 Jan 2017 19:13:25 +0100 Lines: 28 Message-ID: References: <9fc9d84a-b4a7-45a6-a47a-ab7d885bf5ce@googlegroups.com> <0dec1ad1-3625-4ac6-91aa-9b176256554b@googlegroups.com> Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: quoted-printable X-Trace: individual.net RadM3ixtrJ4XKDL1RogK2Q7q8Q8E0bdKQzJcLDUjxPZOnB/XQ= Cancel-Lock: sha1:HVqV5tzNw06sSEQ2wLqeBEy56J4= User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:45.0) Gecko/20100101 Thunderbird/45.5.1 In-Reply-To: Xref: csiph.com comp.lang.java.programmer:36184 On 11.01.2017 01:49, Arne Vajh=C3=B8j wrote: > On 1/10/2017 6:29 PM, Davej wrote: >> I'm having a problem using a redirect because I'm using a filter, and >> the filter doesn't seem to like that. I end up with a 500 error. >> >> One solution seems to be to invalidate the session upon a successful >> login and create a new session for the session member object. I do not think that is necessary, you just need to record proper login=20 state in the session. Creating new sessions eats up entropy and is=20 usually also slower than updating the session instance. > Or you could troubleshoot that filter problem. There must be a reason > and a solution to that problem. > > I would not like to run with a filter that barfs on redirects. Agree. This is a typical use case for using a Filter. Kind regards robert --=20 remember.guy do |as, often| as.you_can - without end http://blog.rubybestpractices.com/