General issues using Chrome recently - CORS, CORB

This is maybe a broader question, not a problem on the Latitude side - but I'm wondering if other Geocortex users have been having issues with Chrome and HTML5 viewer applications.

Our sites are occasionally not fully loading, or not loading at all in Chrome (maybe for the last 6 months or so). Incognito usually works (not always though) - and clearing the browser cache works for a while.

The developer tools indicate that Chrome seems to be hanging on to previously visited sites, and the related Access Control Allow Origin header values - the 'from origin' and Access Control Allow Origin values don't seem to reflect what should be happening when a sight loads.

We have similar things happing in our Portal and AGOL sites, so it seems to be Chrome getting more strict about what it allows.

Just generally wondering if other people have begun to notice similar issues, and if there are any ideas about how to work around it - clearing browser caches regularly is not something many of our users are comfortable with, and some of the sites are public.

Mike Ketler

April 12, 2019 21:59

Hi,

Have you reviewed the KB Article and the Documentation links included below? If you are still having issues then I'd recommend opening a Support Ticket.

https://support.geocortex.com/essentialsGSCkba?id=kA360000000CidV

https://docs.geocortex.com/essentials/latest/install-help/Default.htm#ge/install/cors.htm

Thanks,

Doug Yates

January 13, 2021 18:00

Mike- the support link you included is dead. Can you dig this up and repost?

Permanently deleted user

January 13, 2021 21:16

Hi Doug, the updated link is https://support.geocortex.com/essentialsGSCkbaDetail?sub-nav=kba&main-nav=essentials&id=kA6f200000091QxCAI

General issues using Chrome recently - CORS, CORB

Comments

Didn't find what you were looking for?