Forum Discussion
Thanks .. this fixed it for us !
- Stanislas_Piro2Sep 27, 2018Cumulonimbus
Thanks for the feedback. does it fix the same requirement (Purpose header with prefetch value) or is it a similar requirement base on other criteria?
- Michel_HumphreySep 27, 2018Nimbostratus
we were getting sporadic /my.logout.php3?errorcode=21. errors and this only on chrome .. version 69. Errors were accompanied of unexplained Null values in session variables that should of been populated..
after reading description of issues in this thread.. we figured that multiple queries might be happening for us too .. and parralell queries might the ones without populated variables.. hence the errors.. by essentially "killing" parallele querie.. it seemed to have fixed our issue. And as an unexpected result ... now our access policy also seems to run alot faster.. "snappier" .. i'm sure F5 code is ready for all new chrome features....
i want t osatte this conclusion is in no way scientific .. or by any means technically backed by anything but .. it did'nt work cleanly before the additionnal Irule code .. and now its predictable and snappy.
We did not go into traffic analysis to a level of waht is highlighted in Vinne73 post ..