Https://unpkg.com/gridjs-spreadsheet@23.2.0/xspreadsheet.js returns 520 errors

https://unpkg.com/gridjs-spreadsheet@23.2.0/xspreadsheet.js

request headers from chrome follows:

  1. Request URL:

https://unpkg.com/gridjs-spreadsheet@23.2.0/xspreadsheet.js

  1. Request Method:

GET

  1. Status Code:

520

  1. Remote Address:

104.16.123.175:443

  1. Referrer Policy:

strict-origin-when-cross-origin

  1. Response Headers

  2. cache-control:

private, max-age=0, no-store, no-cache, must-revalidate, post-check=0, pre-check=0

  1. cf-ray:

798f3e058d9a5b11-IAD

  1. content-type:

text/html; charset=UTF-8

  1. date:

Mon, 13 Feb 2023 17:21:45 GMT

  1. expires:

Thu, 01 Jan 1970 00:00:01 GMT

  1. referrer-policy:

same-origin

  1. server:

cloudflare

  1. set-cookie:

cf_use_ob=0; path=/; expires=Mon, 13-Feb-23 17:22:15 GMT

  1. x-frame-options:

SAMEORIGIN

  1. Request Headers

  2. :authority:

unpkg.com

  1. :method:

GET

  1. :path:

/gridjs-spreadsheet@23.2.0/xspreadsheet.js

  1. :scheme:

https

  1. accept:

3./*

  1. accept-encoding:

gzip, deflate, br

  1. accept-language:

en-US,en;q=0.9

  1. cache-control:

no-cache

  1. dnt:

1

  1. pragma:

no-cache

  1. referer:

https:///

  1. sec-ch-ua:

“Not_A Brand”;v=“99”, “Google Chrome”;v=“109”, “Chromium”;v=“109”

  1. sec-ch-ua-mobile:

?0

  1. sec-ch-ua-platform:

“Windows”

  1. sec-fetch-dest:

script

  1. sec-fetch-mode:

no-cors

  1. sec-fetch-site:

cross-site

  1. user-agent:

Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/109.0.0.0 Safari/537.36

@dfreder,

We need to investigate your issue in details. If we require more information or other data, we will ask you. We have opened the following new ticket(s) in our internal issue tracking system and will deliver their fixes according to the terms mentioned in Free Support Policies.

Issue ID(s): CELLSGRIDJS-756

You can obtain Paid Support services if you need support on a priority basis, along with the direct access to our Paid Support management team.

This went away about 10 mins after reporting. the cdn is returning js now

@dfreder,

It seems it was a temporary glitch on your side and now it is working on your end.
Let us know if you still find any issue.

will do, thanks

@dfreder,
You are welcome.