Re: Using CsrfPreventionFilter with GET-based submissions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peter, On 11/12/19 18:52, Peter Kreuser wrote: > > > Chris, > >> Am 13.11.2019 um 02:35 schrieb Christopher Schultz >> : >> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> Peter, >> >>> On 11/10/19 19:05, Peter Kreuser wrote: Chris,

Re: Using CsrfPreventionFilter with GET-based submissions

Chris, > Am 13.11.2019 um 02:35 schrieb Christopher Schultz > : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > Peter, > >> On 11/10/19 19:05, Peter Kreuser wrote: >> Chris, >> >>> >>> Am 09.11.2019 um 03:58 schrieb Christopher Schultz >>> : >>> >>> -BEGIN PGP SIGNED

Re: Using CsrfPreventionFilter with GET-based submissions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Peter, On 11/10/19 19:05, Peter Kreuser wrote: > Chris, > >> >> Am 09.11.2019 um 03:58 schrieb Christopher Schultz >> : >> >> -BEGIN PGP SIGNED MESSAGE- Hash: SHA256 >> >> All, >> >> I'm playing with the CsrfPreventionFilter and

Re: Using CsrfPreventionFilter with GET-based submissions

> All, > > I'm playing with the CsrfPreventionFilter and things are working well > in the following situations: > > link text > > and > > > ... > > > As long as the URL has been passed through request.encodeURL(). > > However, this one is causing me a problem: > > > ... > > > This

Re: Using CsrfPreventionFilter with GET-based submissions

Chris, > > Am 09.11.2019 um 03:58 schrieb Christopher Schultz > : > > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA256 > > All, > > I'm playing with the CsrfPreventionFilter and things are working well > in the following situations: > > link text > > and > > > ... > > > As long as

Using CsrfPreventionFilter with GET-based submissions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm playing with the CsrfPreventionFilter and things are working well in the following situations: link text and ... As long as the URL has been passed through request.encodeURL(). However, this one is causing me a problem: ... This