topic Re: Library is not coming from Accept CDN. in Integration and Testing

Library is not coming from Accept CDN.

tan — Tue, 04 Apr 2017 19:04:17 GMT

Hey. A client has reached out to me with the following error message:

Please include Accept.js library from cdn.

And in the console:

Library is not coming from Accept CDN.

However the library is coming from the CDN. I have been unable to reproduce the error without actually loading it from somewhere else. The client has already tried clearing the browser cache. What else could be causing this issue?

Thank you.

Re: Library is not coming from Accept CDN.

RichardH — Tue, 04 Apr 2017 19:56:14 GMT

@tan

Could you share your code so we can see how you're calling Accept.js?

Richard

Re: Library is not coming from Accept CDN.

tan — Tue, 04 Apr 2017 20:18:38 GMT

Here it is.

<script type='text/javascript' src='https://js.authorize.net/v1/Accept.js'></script>

It works for me. I tested it in 3 different browsers.

Re: Library is not coming from Accept CDN.

RichardH — Tue, 04 Apr 2017 20:30:24 GMT

Try adding the character set command and see if that helps.

  <script type="text/javascript" src="https://js.authorize.net/v1/Accept.js" charset="utf-8"></script>

Richard

Re: Library is not coming from Accept CDN.

tan — Tue, 04 Apr 2017 20:40:55 GMT

Would the following tag have the same effect?

<meta http-equiv="Content-Type" content="text/html; charset=UTF-8" />

I have that at the top of the page. The recommended way to add scripts on the platform we're using does not give us the ability to add any attributes to the script tag itself. If this was the problem, would it not cause the same error for everyone? I have had no such errors on my end and I have tested it in Chrome, Firefox, and Edge. Also, some Googling tells me that a missing charset would result in a different error. Thanks.

Re: Library is not coming from Accept CDN.

Aaron — Wed, 05 Apr 2017 18:58:44 GMT

Hi @tan,

The script itself is doing some integrity checking to see if it's intact and served from the right place. If a browser loads the script but interprets it with a different encoding, those checks could fail on that browser.

Can you test your site on your end, but change your browser's encoding to a different charset and see if you can duplicate the error?

Re: Library is not coming from Accept CDN.

tan — Wed, 05 Apr 2017 19:53:37 GMT

Hey @Aaron. Thanks for your help. I tried using a few different character encodings but I was unable to reproduce the error. What other checks could be failing?

Re: Library is not coming from Accept CDN.

dustin1 — Wed, 05 Apr 2017 20:49:57 GMT

Trying to debug a third-party's browser is quite difficult!

I imagine it could also be other factors such as plugins. Have you had the client try an incognito chrome, or private browsing firefox mode?

Re: Library is not coming from Accept CDN.

tan — Wed, 05 Apr 2017 21:39:35 GMT

Yeah, they tried private browsing in Chrome and Firefox.

Re: Library is not coming from Accept CDN.

Aaron — Thu, 06 Apr 2017 00:08:07 GMT

@tan wrote:

Hey @Aaron. Thanks for your help. I tried using a few different character encodings but I was unable to reproduce the error. What other checks could be failing?

The main check is just the source of the script. Accept.js script calls another script on our site (AcceptCore.js) which is basically checking the source URL of the first script. If that URL doesn't match https://js.authorize.net/v1/Accept.js, it throws the error.

If that customer's browser is seeing that the script has a different source, I might start to be concerned about some really aggressive cache upstream that somehow is serving redirects instead of content, or possibly some malware on the customer's end. I'm trying to think of other ways this could fail and am coming up blank.

Re: Library is not coming from Accept CDN.

tan — Thu, 06 Apr 2017 13:16:43 GMT

Hey. I discovered what the problem is. The client appears to have a plugin on their website that is adding a query argument "?ver=4.5.7" to the end of every script tag "src". This is presumably for cache control purposes. Now that I know what the problem is, I can work on a solution.

Thank you very much to everyone who helped.

Re: Library is not coming from Accept CDN.

Aaron — Thu, 06 Apr 2017 15:54:30 GMT

Oh wow. That's great that you found it, and thanks immensely for coming back with the update. Now that's something we can remember to check if we here any other report. I don't know how common this method of cache control would be, so I don't know if it's worth our while to investigate any accomodations on our end. We could, for example, only attempt to match the URL up to any query string given.

In the short term, we could possibly put something in the documentation that says we verify where the script was loaded from, and we do that by actually comparing the URL string against what we know to be correct, so don't do anything that might break that.

Again, thanks!

Re: Library is not coming from Accept CDN.

tan — Thu, 06 Apr 2017 19:51:11 GMT

Hey. Sorry, I was mistaken. It's actually WordPress adding the query argument, not a plugin.

Re: Library is not coming from Accept CDN.

GRKAUTHNET8 — Sun, 20 Oct 2019 01:19:31 GMT

Hello,

I am seeing the same problem on my end.

The jquery is automatically adding ?=timestamp to https://jstest.authorize.net/v1/Accept.js which I fixed by temporarily disabling cache while loading the Accept.js script.

However, I now see the error on the AcceptCore.js. I can confirm that the dynamic ?=[timestamp] is no longer sent, but still I am getting 90:97 Library is not coming from Accept CDN.

https://jstest.authorize.net/v1/AcceptCore.js

0 !== document.querySelectorAll('script[src="' + c + '"]').length || k(z, b) || (y.warn("Library is not coming from Accept CDN."), m(b, C.messageInfo.E_WC_01)), "https:" === window.location.protocol || k(z, a) || (y.warn("An HTTPs connection is required to secure delivery of payment information."), m(a, C.messageInfo.E_WC_02))

Did anybody encounter this, how do I fix this ?

Any help is highly appreciated.

Thank you.

Re: Library is not coming from Accept CDN.

GRKAUTHNET8 — Sun, 20 Oct 2019 01:28:35 GMT

Hello,

I am seeing the same problem on my end.

The jquery is automatically adding ?=timestamp to https://jstest.authorize.net/v1/Accept.js which I fixed by temporarily disabling cache while loading the Accept.js script.

However, I now see the error on the AcceptCore.js. I can confirm that the dynamic ?=[timestamp] is no longer sent, but still I am getting 90:97 Library is not coming from Accept CDN.

https://jstest.authorize.net/v1/AcceptCore.js

Did anybody encounter this, how do I fix this ?

Any help is highly appreciated.

Thank you.

Re: Library is not coming from Accept CDN.

GRKAUTHNET8 — Wed, 06 Nov 2019 23:02:18 GMT

Any update/resolution to the issue I posted ?

Re: Library is not coming from Accept CDN.

haveigonemental — Mon, 17 Aug 2020 05:18:54 GMT

I just ran into this issue on a Wordpress site, it's because Wordpress automatically adds a query string to the end of js and css files. In this particular instance it was still adding them despite having nulled the version number when enqueue'ing the script.

I had to use this code snippet to remove the query string from only Accept.js and fix the issue.

// remove version from scripts and styles
function remove_version_scripts_styles($src) {
    if (strpos($src, 'Accept.js')) {        $src = remove_query_arg('ver', $src);
    }
    return $src;
}add_filter('script_loader_src', 'remove_version_scripts_styles', 9999);

I think it's a little ridiculous that a query string could break the whole thing, but this did the trick.