ERR_ABORTED 400 in Chrome when using the "save button" addon

[nekhbet]

I notice in the Chrome's devtools that a page I'm working on always shows the pinterest widget failing.

Example URL: https://www.allnumis.com/coins-catalog/finland/republic-1991-1999/10-markkaa-1997-45098

Screenshot attached.

The only code I have there, relating to pinterest is:

<script
    type="text/javascript"
    async defer
    src="//assets.pinterest.com/js/pinit.js"
    data-pin-hover="true"
></script>

What do I do wrong?

Thanks!

[hreilly]

I'm also having this same error, but I don't think it's an error with the widget failing. It's the GET request to the log url that seems to be failing. The widget is working just fine for me in terms of rendering and pin functionality, both vanilla and with custom params. No other errors on page. Below is the full error message I'm receiving.

Someone has also mentioned the issue a couple weeks ago in this very old, semi-related thread. https://github.com/pinterest/widgets/issues/10#issuecomment-577656368

I was able to get a 200 response when the "type=pidget" param was removed from the full url.

[jeanadev]

In investigating this issue myself, I loaded a page in Firefox to see if I got the same error. I did not get the ERR_ABORTED error in Firefox that I got in Chrome, BUT I did get this warning:

The script from “https://log.pinterest.com/?type=pidget&guid=SVDuhRP1GBiN&tv=…in-causes-and-remedies&callback=PIN_1581459223659.f.callback[0]” was loaded even though its MIME type (“”) is not a valid JavaScript MIME type.

So, I'm wondering if this is still a pinterest issue, and not a user issue.

[nekhbet]

MIME type should be Content-Type header which is not set:

> GET /?type=pidget&guid=SVDuhRP1GBiN&tv=…in-causes-and-remedies&callback=PIN_1581459223659.f.callback[0] HTTP/2
> Host: log.pinterest.com
> User-Agent: curl/7.58.0
> Accept: */*
> 
* Connection state changed (MAX_CONCURRENT_STREAMS updated)!
< HTTP/2 400 
< accept-ranges: bytes
< date: Wed, 12 Feb 2020 05:38:12 GMT
< via: 1.1 varnish
< x-served-by: cache-lcy19230-LCY
< x-cache: MISS
< x-cache-hits: 0
< x-timer: S1581485893.756646,VS0,VE78
< content-length: 0

So not client fault.

[SassNinja]

The error seems to be related to the browser's do-not-track setting (at least in my case)

When I disable it the error is gone