Issues with Chrome "prefetching" our IdP pages

[alessandro at avagliano.berlin]

On 26.09.18 14:06, Feyaerts Vincent wrote:

> I tried sending a 403 as a response to the Prefetch request, but then
> Chrome just stops and won’t ask again.
>
This chrome prefetch behavior is getting very annoying for us as well.
We were able to observe it while intercepting the chrome traffic and is
typically done while writing an SP address in the chrome bar, before
pressing "enter". 

We are also testing the "403" response workaround, using the following
code in our NGINX front-end on a test system:

  if ($http_purpose ~* "prefetch") {
    return 403;
  }

which seemed to work quite well so far. Can you provide some more
details on why the 403 is not working for you?

we didn't notice any issue so far in our tests: as chrome
(69.0.3497.100) will get a 403 to the prefetch request in the
background, then after the user press enter, chrome will make the second
request (without the prefetch header) which will be successfully served
(tested with IDP 3.3.3)


Regards,
Alessandro

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20181015/812bcd28/attachment.html>