Somehow similar (and not adressed by my fix) is that Chrome is doing
"random" GET requests when you type an URL to provide auto-completion.
I assume that this is less likely to hit a Seaside callback, but we
should still pay attention.
On Wednesday, 9 March 2011, Julian Fitzell <jfitzell(a)gmail.com> wrote:
This is, of course, part of the problem with using GET requests for
callbacks... shame you can't specify POST in an href anchor... :)
On Mon, Mar 7, 2011 at 6:00 PM, Lukas Renggli <renggli(a)gmail.com> wrote:
> That was a tricky one:
> Unfortunately the Mozilla engine does prefetching of some "random"
> links on websites
> aggressive prefixing is a highly controversial topic even in the
> FireFox community itself, because of all kinds of issues.
> Now obviously this prefetching is generally something we don't want to
> happen with Seaside applications as callbacks could unwillingly be
> triggered. I changed the Seaside code to deny all prefetch requests in
> WAApplication. This should solve the problem:
> Name: Seaside-Core-lr.711
> Author: lr
> Time: 7 March 2011, 6:52:15 pm
> UUID: 57d701cc-b90b-458d-9f7a-cf9a493a9997
> Ancestors: Seaside-Core-dkh.710
> - added a tester for prefetch requests
> Name: Seaside-Session-lr.135
> Author: lr
> Time: 7 March 2011, 6:53:50 pm
> UUID: 07b0af88-64b7-4bcb-8778-d14e448dddd9
> Ancestors: Seaside-Session-pmm.134
> Lukas Renggli
> seaside-dev mailing list