[Seaside-dev] Re: Enabling cookies causes callback links to incorrectly redirect in Firefox

[Philippe Marschall]

2011/3/7 Lukas Renggli <renggli at gmail.com>:
> That was a tricky one:
>
> Unfortunately the Mozilla engine does prefetching of some "random"
> links on websites
> (https://developer.mozilla.org/en/Link_prefetching_FAQ). This
> 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

I'm wondering if not implemented (501) is the right error code. That
is in there because we only support GET and POST. But the prefetch is
a GET and we support that, just not as a prefetch. 5xx indicates a
server error, maybe bad request (400) or something other in the 4xx
range that signals a client error would be better.

Cheers
Philippe