Hi
For some time I'm facing an issue with Safari browser. For every page in my domain Safari sends wrong user agent. It introduces itself as a version 12 even though in reality it is version 14 from BigSur. In the result every external service which relies on a browser version is broken (such as analytics or ad campaigns). Clicking in development tab a "Disable Site-specific hacks" option fixes the issue and the user agent header becomes proper. With the option disabled it looks like: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.2 Safari/605.1.15
According to documentation Safari tries to fix issues with my page but enabling or disabling the site-specific hacks option doesn't change the output in a browser console so I don't know what exactly is wrong with my page.
I got two questions:
For some time I'm facing an issue with Safari browser. For every page in my domain Safari sends wrong user agent. It introduces itself as a version 12 even though in reality it is version 14 from BigSur. In the result every external service which relies on a browser version is broken (such as analytics or ad campaigns). Clicking in development tab a "Disable Site-specific hacks" option fixes the issue and the user agent header becomes proper. With the option disabled it looks like: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_6) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/12.1.2 Safari/605.1.15
According to documentation Safari tries to fix issues with my page but enabling or disabling the site-specific hacks option doesn't change the output in a browser console so I don't know what exactly is wrong with my page.
I got two questions:
Is it possible to disable "site-specific hacks" functionality using http headers, meta tags or any other site development technique rather than clicking in dev tools?
Who decides and where to get information why our page was marked as broken and what actions we have to initiate to remove our page from "site-specific hacks"
