[Seaside-dev] Seaside and CSRF attacks

[Philippe Marschall]

On Tue, Aug 21, 2018 at 11:30 PM tim Rowledge <tim at rowledge.org> wrote:
>
>
>
> > On 21-08-2018, at 1:07 PM, Esteban A. Maringolo <emaringolo at gmail.com> wrote:
> >
> > Hi,
> >
> > On 21/08/2018 16:44, Max Leske wrote:
> >
> [snip useful stuff]
>
> > I'm working with Seaside in VW, let me know if you need any further help
> > with that. Seaside in VW isn't as updated as in other platforms.
>
> Thanks; what would be really useful to me (and I feel it would make a good explanatory page for the seaside.st site as well) would be pointers to the right basic class(es) and methods to provide a simple example of the sequence of events that we get.
>
> With much hand-waving I guess we might be able to say something like -

The actions are stored in a WACallbackRegistry in a WARenderContext in
a WARenderLoopContinuation which are then processed in
WACallbackProcessingActionContinuation >> #basicPerformAction which is
called by WASession >> #handleFiltered:

Setting breakpoints in

WACallbackRegistry >> #store:

WASession >> #actionUrlForContinuation:

WACallbackProcessingActionContinuation >> #basicPerformAction

should get you started.

Cheers
Philippe