Re: Enabling cookies causes callback links to incorrectly redirect in Firefox

> 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:

> 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
>
> Lukas
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>

> This is, of course, part of the problem with using GET requests for
> callbacks... shame you can't specify POST in an href anchor... :)
>
> Julian
>
> On Mon, Mar 7, 2011 at 6:00 PM, Lukas Renggli <[hidden email]> wrote:
>> 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
>>
>> Lukas
>>
>> --
>> Lukas Renggli
>> www.lukas-renggli.ch
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>

> 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

> 2011/3/7 Lukas Renggli <[hidden email]>:
>> 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
> _______________________________________________
> seaside-dev mailing list
> [hidden email]
> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>

> Yeah, I was not sure about that one either, but didn't know a better
> error code. How are other web frameworks dealing with this?
>
> Lukas
>
> On 13 March 2011 18:43, Philippe Marschall <[hidden email]> wrote:
>> 2011/3/7 Lukas Renggli <[hidden email]>:
>>> 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
>> _______________________________________________
>> seaside-dev mailing list
>> [hidden email]
>> http://lists.squeakfoundation.org/mailman/listinfo/seaside-dev
>>
>
>
>
> --
> Lukas Renggli
> www.lukas-renggli.ch
>