topic Re: (E_WC_03) Accept.js is not loaded correctly in Integration and Testing

(E_WC_03) Accept.js is not loaded correctly

felixmaier1989 — Tue, 07 Mar 2017 11:26:21 GMT

Today I was back at work after a few days off and when I tested paying via Accept.Js on my local environment, I had the following error message:

(E_WC_03) Accept.js is not loaded correctly

But after refreshing the page the error was gone. I was not able to reproduce the bug because I ran out of time. I believe this lies in this hash-logic which ensures compatibility between Accept.js and AcceptCore.js. Are you sure this pairing is robust against browser caching?

Why wouldnt you allow passing query parameters to https://jstest.authorize.net/v1/Accept.js ? I think is it very important that the front end can force the JS file not to be loaded from the cache with some inclusion like:

<script type="text/javascript" src="https://jstest.authorize.net/v1/Accept.js?version=<?php echo time(); ?>" charset="utf-8"></script>

Otherwise, as third-part developers implement your library and you have no control over their front end code, you cannot ensure backward compatibility.

-------------------

FYI: steps to reproduce

What I exactly did before having this bug:

1) I openend my browser (Firefox, under OSX) and made some payments (on my local dev environment) from my website to my sandbox account.

2) Three days later, I try to another payment, but on the page load (my app runs with PHP) an error "

(E_WC_03) Accept.js is not loaded correctly" is thrown

3) Assuming this is a caching issue, I change

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

<script type="text/javascript" src="https://jstest.authorize.net/v1/Accept.js?version=<?php echo time(); ?>" charset="utf-8"></script>

in my page to force refreshing the JS file. When refreshing the page, my console says "Library is not coming from Accept CDN."

4) After reverting my change and refreshing the page, the initial error E_WC_03 was gone and I could place the payment.

Re: (E_WC_03) Accept.js is not loaded correctly

Aaron — Tue, 07 Mar 2017 18:29:22 GMT

Hi @felixmaier1989,

Within the last day, we've updated the Accept.js and AcceptCore.js components, so if your browser was indeed caching an old version, that might have caused some problems. If there's any time that you'd see a similar issue when we haven't just updated the script, we'd definitely need to look into that.

In the meantime, I'll pass on your suggestions to see if there's anything else we can do to avoid cache-related errors around the time of an update to the scripts on our end.

Re: (E_WC_03) Accept.js is not loaded correctly

msupko88 — Mon, 20 Mar 2017 23:47:54 GMT

Hi @Aaron!

Just wanted to add a +1 for cache-busting for Accept.js. Our site has had several users, both customers and administrators, report E_WC_03 over the last couple of weeks. In each case, clearing browser cache or opening a private session has resolved the issue.

It's definitely a problem we'd like to see addressed sooner than later, as it's costing us at least some business.

Thanks,

Matt

Re: (E_WC_03) Accept.js is not loaded correctly

Aaron — Tue, 21 Mar 2017 17:59:02 GMT

In my testing, the jstest and js.authorize.net servers both respond properly to browser requests when the browser has a cached version in play and the browser is doing the right thing. The browser will send an etag, and ask for a changed version if there's a change after the specified date, the server will respond with a 304 status code if it's not changed, and so on.

However, there are browser versions that may be buggy, and there are browser misconfigurations, and misbehaving proxies, and all manner of other things that could go wrong there. So, if we can improve things with the right Cache-control: header in the response, for example, that would be nice.

Edit: I originally suggested a workaround here that won't actually work since the AcceptCore.js script verifies the URL it was called from. If I had a better memory than a gnat, I would have remembered that Felix already tried the same thing with the same results upthread.

Re: (E_WC_03) Accept.js is not loaded correctly

nadin — Thu, 12 Oct 2017 14:31:33 GMT

I actually still getting this error the only solution was to clear the cache of the browser but its on AccceptCore.js so maybe its just better if you guys can add a header to remove the cache completly on that file its not a big file so will not affect the performance

This is how I'm including the file

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

BTW: Testing with chrome Version 61.0.3163.100 (Official Build) (64-bit)

Re: (E_WC_03) Accept.js is not loaded correctly

losrobots — Thu, 12 Oct 2017 18:26:39 GMT

Just want to say this is happening to me as well as of this morning. Several customers called up complaining. Hopefully someone at authorize.net sees this soon.

Re: (E_WC_03) Accept.js is not loaded correctly

RichardH — Thu, 12 Oct 2017 18:51:53 GMT

Hello

If you're experiencing issues with your live production account, for fastest service we recommend contacting customer support by phone at 877-447-3938.

Richard

Re: (E_WC_03) Accept.js is not loaded correctly

ryanhoerr — Thu, 12 Oct 2017 18:55:27 GMT

We've gotten reports of this from customers today as well. The Accept.js libraries need to be robust against browser caching.

Re: (E_WC_03) Accept.js is not loaded correctly

ncallaway — Thu, 12 Oct 2017 19:17:20 GMT

The same thing is occurring for us. It looks like inconsistent versions of Accept.js and AcceptCore.js are being served from the CDN, which causes the failure.

Re: (E_WC_03) Accept.js is not loaded correctly

wkirby — Thu, 12 Oct 2017 19:42:55 GMT

Contacting support by phone was absolutely useless. Phone support was not remotely technical, and was not able to escalate the issue. More problematic, phone support didn't seem aware that Accept.js was a first-party product supported by Authorize.net.

This definitely appears to be a CDN based issue; our team's best guess is a failed rollout of an update to the AcceptCore.js file to some servers.

Based on interaction with support, we will be moving payment processing to another provider.

Re: (E_WC_03) Accept.js is not loaded correctly

Aaron — Thu, 12 Oct 2017 20:37:12 GMT

Thanks for posting here everyone, and sorry about any difficulties you've been experiencing. We're investigating, and it looks like there was a CDN caching issue that's now been resolved. In the short term, refreshing the browser cache should clear up any lingering effects.

@wkirby, I'm so sorry about your experience with support. The heads of the support organization have been made aware so that they can investigate whatever retraining might be necessary.

Re: (E_WC_03) Accept.js is not loaded correctly

aviseu — Thu, 12 Oct 2017 21:13:59 GMT

Hey everyone.

I confirm that AcceptCore.js has changed on the CDN (not sure about Accept.js).

Both files of the older version work, and both files of the newer version work. But since the URLs are the same I'm guessing for whatever reason we are having one of the files being cached and not the other, causing a version mismatch.

This is troubling because we have no control over our user's browser cache. Unfortunately cache busting Accept.js doesn't propagate the same effect to AcceptCore.js

To get around this issue I decided to try forcing the cacheless loading of both files (Accept.JS and AcceptCore.js).

I'm still confirming that this indeed clutched the issue but I here is what (appears) to have worked:

Original Code:

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

New Code:

<script>
                $.ajaxSetup({
                    cache: true
                });

                function loadScript(script) {
                    jQuery.ajax({
                        async: false,
                        type: 'GET',
                        url: script,
                        data: null,
                        success: function () {
                            console.log(script + ' force loaded');
                        },
                        dataType: 'script',
                        error: function (xhr, textStatus, errorThrown) {
                            console.log(script + ' ' + textStatus);
                        }
                    });
                }

                loadScript('https://js.authorize.net/v1/AcceptCore.js');
                loadScript('https://js.authorize.net/v1/Accept.js');
            </script>
            <script type="text/javascript" src="https://js.authorize.net/v1/Accept.js" charset="utf-8"></script>

This, I hope, forces the fetching of the new versions of the Javascript files, which should then be used when the <script> tag requests it. Requesting it only with jQuery.ajax seems to trigger some sort of CDN enforcement protection so the <script> is still needed.

Hoping this helps anyone who is pulling their hairs out like I was.

Ideally in the future Authorize.net would be more careful with version changes on their CDN.

Re: (E_WC_03) Accept.js is not loaded correctly

JoshK1 — Mon, 16 Oct 2017 15:10:31 GMT

Can you specify the amount of time this would impact customers without having cleared their browser cache?

Re: (E_WC_03) Accept.js is not loaded correctly

aviseu — Wed, 18 Oct 2017 02:07:32 GMT

Just checking in. We are still having this issue with users using iOS (safari) and OS X (chrome or safari). No idea what else I can do.

Re: (E_WC_03) Accept.js is not loaded correctly

wangleitj77 — Thu, 24 Oct 2019 18:15:57 GMT

This happened again, our test envionment got same error.

Re: (E_WC_03) Accept.js is not loaded correctly

icible — Tue, 29 Oct 2019 20:24:38 GMT

I confirm that this exact issue is back.

For the past week or so.

Re: (E_WC_03) Accept.js is not loaded correctly

icible — Tue, 29 Oct 2019 20:25:57 GMT

Yes, this issue is back.

For the past week or so

Re: (E_WC_03) Accept.js is not loaded correctly

piyush_kt — Wed, 06 Nov 2019 13:04:20 GMT

It's happening for us in our Test environment.

The issue is not happening for all users but some users are affected and not able to submit test payments.

Re: (E_WC_03) Accept.js is not loaded correctly

dusanmisic — Fri, 08 Nov 2019 12:57:25 GMT

The same is here and also lasts for several days...

Our testing environment is affected.

Re: (E_WC_03) Accept.js is not loaded correctly

jonathan2019 — Thu, 02 Jan 2020 18:17:50 GMT

Hello!

Wouldn't you use cache: false to prevent the script from being cached?
When I used this method of loading the script in a sandbox environment, the transaction went through normally. The test credit card was accepted. But it did not show up in a transaction search.