Logging plausible event results in CORS error about analytics HOT 6 CLOSED

I have reproduced the issue and will get back to you.

from analytics.

Hi @codemonkey800

I think the problem originates from this package: https://www.npmjs.com/package/axios-cache-interceptor?activeTab=readme

Please see https://github.com/arthurfiorette/axios-cache-interceptor/blob/ad69e6d6e491cfa5fe2cb542bc90fd205fc823e3/docs/src/config/request-specifics.md#cachecachetakeover

in particular this bit:

Please try the fallback suggested and see if the OPTIONS XHR requests are handled then.

from analytics.

FWIW the problem occurs only for that button:

and not that one:

Even though both trigger a new tab link.
That should help you figure out the difference

from analytics.

closing this now but feel free to contact our support if you have any further questions

from analytics.

@metmarkosaric i am struggling with the same issue. What exactly is meant with the fallback?

from analytics.

i am using Plausible with vercel. Does that look like the correct setting?

//vercel.json

{
    "headers": [
        {
            "source": "/(.*)",
            "headers": [
                {
                    "key": "Cache-Control",
                    "value": "max-age=0, s-maxage=86400, stale-while-revalidate=59"
                },
                {
                    "key": "Access-Control-Allow-Headers",
                    "value": "Cache-Control, Pragma, Expires"
                }
            ]
        }
    ]
}

from analytics.