topic Re: Accept.js - Sandbox: Library is not coming from Accept server in Integration and Testing

Accept.js - Sandbox: Library is not coming from Accept server

jrm89 — Wed, 23 Oct 2019 20:31:04 GMT

Today I attempted to deploy me application to a DEV server and I started getting the following error: Library is not coming from Accept server--- a7e38542d3a404b4b3ac37a7252bca2e7f3dd724a357aa93ce22f413e74333c3

Here is the script I'm including:

It works fine if you do the production url (js.authorize.net), but it stopped working for me today when using the sandbox url. I don't know what is happening. To cut down on all variables, I literally created a blank html document with this script tag in the header and I still get the error message in the console. It happens in chrome, firefox, and edge. I've been testing successfully the last several days with no issues. I'm stumped at the moment. Anyone run across this?

Re: Accept.js - Sandbox: Library is not coming from Accept server

jasonb — Wed, 23 Oct 2019 21:05:04 GMT

I'm seeing the exact same issue. Using jstest.authorize.net leads to "Library is not coming from Accept server" error in Accept.js when loading AcceptCore.js from jstest.authorize.net. FireFox, Safari, Chrome. Plugins disabled.

Re: Accept.js - Sandbox: Library is not coming from Accept server

cmchristensen — Wed, 23 Oct 2019 21:36:16 GMT

I am seeing the issue as well. We discovered after updating to Chome version 78 (and clearing cache) today - Firefox 70 seems to have the same problem as well.

Chrome 77 gives this warning:
A cookie associated with a cross-site resource at http://authorize.net/ was set without the `SameSite` attribute. A future release of Chrome will only deliver cookies with cross-site requests if they are set with `SameSite=None` and `Secure`. You can review cookies in developer tools under Application>Storage>Cookies and see more details at https://www.chromestatus.com/feature/5088147346030592 and https://www.chromestatus.com/feature/5633521622188032.

Perhaps this warning will give insight?

Re: Accept.js - Sandbox: Library is not coming from Accept server

dliv-gw — Wed, 23 Oct 2019 21:39:06 GMT

We are having the same problem:

- starting today

- in the sandbox

- using the hosted form variant (AcceptUI.js)

This can be easily reproduced by:

- take the code sample at: https://developer.authorize.net/api/reference/features/acceptjs.html#Example_of_the_Complete_HTML_Page

- ensure you're using the "Hosted Form" sample

- update with your apiLoginID and clientKey

- serve the page with a static file server

- see console warning: Library is not coming from Accept server---a7e38542d3a404b4b3ac37a7252bca2e7f3dd724a357aa93ce22f413e74333c3

- add a card

- see console error: E_WC_03: Accept.js is not loaded correctly

In our testing, the error appears to be specific to AcceptUI.js and not the Accept.js library version ("Your Own Payment Form"). If it is a CDN / caching issue, this could vary...

This appears to relate to past issues:

- https://community.developer.authorize.net/t5/Integration-and-Testing/E-WC-03-Accept-js-is-not-loaded-correctly/td-p/57171

- https://community.developer.authorize.net/t5/Integration-and-Testing/Library-is-not-coming-from-Accept-CDN/td-p/57521

Re: Accept.js - Sandbox: Library is not coming from Accept server

cmchristensen — Wed, 23 Oct 2019 21:53:53 GMT

We are seeing the issue with both AcceptUI.js (hosted payment form), as well ass the Accept.js (own payment form) libraries.

Re: Accept.js - Sandbox: Library is not coming from Accept server

Fallenstedt — Wed, 23 Oct 2019 22:56:18 GMT

We have noticed there is a potential issue between

https://js.authorize.net/v1/Accept.js (Production)
https://jstest.authorize.net/v1/Accept.js (Sandbox)

We noticed that both expected hashes are identical on both scripts. Upon hashing the Production AcceptCore.js, we noticed it matched the Sandbox and Production Accept.js expected hash of (79ec52f0ce86fb27c47d1f860ba62d34ad5fe6cd3778ee0952ac698f52096e81).

Upon hashing the Sandbox AcceptCore.js, we noticed it did not match either with a result hash of (a7e38542d3a404b4b3ac37a7252bca2e7f3dd724a357aa93ce22f413e74333c3).

Is there a possibility the Sandbox Accept.js is using the Production copy instead of the Sandbox copy?

Hopefully someone from Authroize.net can confirm this soon.

Re: Accept.js - Sandbox: Library is not coming from Accept server

Fallenstedt — Wed, 23 Oct 2019 22:58:00 GMT

You can reproduce this via bash:

curl https://js.authorize.net/v1/Accept.js -H 'Cache-Control: no-cache'
curl https://jstest.authorize.net/v1/Accept.js -H 'Cache-Control: no-cache'

curl https://js.authorize.net/v1/AcceptCore.js -H 'Cache-Control: no-cache' -o output.txt
curl https://jstest.authorize.net/v1/AcceptCore.js -H 'Cache-Control: no-cache' -o test_output.txt
shasum -a 256 output.txt
shasum -a 256 test_output.txt

Re: Accept.js - Sandbox: Library is not coming from Accept server

AdamT — Thu, 24 Oct 2019 00:25:53 GMT

We believe that was have identified and resolve the cause of this issue. Can you please try again?

Thank you.

-Adam

Re: Accept.js - Sandbox: Library is not coming from Accept server

Fiala1904 — Thu, 24 Oct 2019 01:36:54 GMT

It still is not working for me.

Re: Accept.js - Sandbox: Library is not coming from Accept server

litza — Thu, 24 Oct 2019 13:59:56 GMT

What a relief to discover this thread - we've been having the same experience during the past few days on our development server. Unfortunately it's still not working for us this morning.

Re: Accept.js - Sandbox: Library is not coming from Accept server

tguenther — Thu, 24 Oct 2019 14:23:26 GMT

It looks like it is working for some users and not others. Why is this error only showing up for some users? Is there something we can do on our end to ensure that this error doesn't occur.

Re: Accept.js - Sandbox: Library is not coming from Accept server

AdamT — Thu, 24 Oct 2019 14:38:44 GMT

Hello,

If you are still experiencing this error, please attempt to clear your browser's cache and test again. If you are continuing to experience this error/issue with Accept.js, please contact Authorize.Net support to provide additional information and details for us to investigate further.

Thank you.

-Adam

Re: Accept.js - Sandbox: Library is not coming from Accept server

Fallenstedt — Thu, 24 Oct 2019 15:39:32 GMT

Hi,

How can we best contact Authroize.Net support for this? I ask because Authorize.net support told me to make a post on the forum. At this point I feel like I am going in circles.

Re: Accept.js - Sandbox: Library is not coming from Accept server

cmchristensen — Thu, 24 Oct 2019 17:34:30 GMT

Note to everyone: I think you need to clear your cache AND cookies. It appears to be working again for me.

@AdamT Could you explain what the issue was and what resolved it?

Re: Accept.js - Sandbox: Library is not coming from Accept server

Fallenstedt — Thu, 24 Oct 2019 17:42:39 GMT

For people getting mixed results, this might be a CDN issue now. It works in chrome after clearing cache + cookies and in an incognito browser. Firefox has been hit or miss.

Re: Accept.js - Sandbox: Library is not coming from Accept server

Fiala1904 — Thu, 24 Oct 2019 17:56:44 GMT

I tested with the Edge browser, which I thought I had never ever used with authorize.net before, and I still got the error. However, after I cleared all my history, it does now work on Edge.

Likewise on Chrome, which I rarely use, I still got the error but after clearing everything it now works on Chrome.

After clearing all my history on Firefox, I continue to get the error. Firefox is where I really need to have it fixed.

Re: Accept.js - Sandbox: Library is not coming from Accept server

AdamT — Thu, 24 Oct 2019 18:07:01 GMT

The issue was caused by an uninteneded change related to the final migration from Akamai to Cloudflare for our Sandbox environement. The issue was minification of javascript related to jstest.authorize.net which was already being done. Once we disabled that function and cleared the cache we started to see this issue resolve and able to successfully call Accept.js.

Re: Accept.js - Sandbox: Library is not coming from Accept server

wangleitj77 — Thu, 24 Oct 2019 18:26:42 GMT

We still got this issue on Firefox/Chrome/Safari, clean cache and history did not solve.

The minify problem is not for Accept.js , it's for AcceptCore.js, we still got 2 character smaller file size.

Re: Accept.js - Sandbox: Library is not coming from Accept server

litza — Fri, 25 Oct 2019 17:03:55 GMT

Unfortunately I'm still experiencing this problem as well, even after clearing all browser data, and even using a browser that I'd never opened the site in.

Re: Accept.js - Sandbox: Library is not coming from Accept server

dailystandard — Fri, 25 Oct 2019 17:32:13 GMT

The cloudflair server I am connecting to still hasn't gotten the updated config for AcceptCore.js. Here are the response headers for AcceptCore.js.

access-control-allow-origin: *
age: 542
cache-control: public, max-age=432000
cf-bgj: minify
cf-cache-status: HIT
cf-polished: origSize=9065
cf-ray: 52b5d5ee99c3c8fb-CMH
content-encoding: br
content-type: application/javascript
date: Fri, 25 Oct 2019 17:15:59 GMT
etag: W/"092b352f68d51:0"
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Wed, 30 Oct 2019 17:15:59 GMT
last-modified: Tue, 10 Sep 2019 23:26:44 GMT
server: cloudflare
status: 200
vary: Accept-Encoding
x-content-type-options: nosniff

It looks like Accept.js is not being minified:

access-control-allow-origin: *
age: 542
cache-control: public, max-age=432000
cf-cache-status: HIT
cf-ray: 52b5d5ee69b4c8fb-CMH
content-encoding: br
content-type: application/javascript
date: Fri, 25 Oct 2019 17:15:59 GMT
etag: W/"ee04d96a369d51:0"
expect-ct: max-age=604800, report-uri="https://report-uri.cloudflare.com/cdn-cgi/beacon/expect-ct"
expires: Wed, 30 Oct 2019 17:15:59 GMT
last-modified: Thu, 12 Sep 2019 19:52:19 GMT
server: cloudflare
status: 200
vary: Accept-Encoding
x-content-type-options: nosniff