search

jquery / codeorigin.jquery.com

jQuery CDN
https://releases.jquery.com
Other
57 stars 605 forks source link

https://code.jquery.com can't be opened. 打不开网站 #65

Closed WuLex closed 2 years ago

WuLex commented 3 years ago

https://code.jquery.com/jquery-3.3.1.min.js 打不开 ,有什么地域限制吗？

2020
brianwarner commented 3 years ago

Hi @WuLex, we are working with support at the CDN to figure out what's wrong. They are looking at the logs, but need some additional info. Can you please provide your public IP address or a tracert to code.jquery.com? You can email them to me directly at operations@openjsf.org.

etshy commented 3 years ago

is there any news about this issue ? I have the same screen (seems to be the same screen as I don't read chinese). I tried to reset my chrome by clearing all data but it still doesn't work.

I noticed this error by visiting the website secretlab.eu that use the code.jquery.com cdn.

It worked for a while using firefox and opera but now it doesn't work anymore.

Edit : It seems on firefox and opera it works "randomly" but chrome fails every time.

Krinkle commented 3 years ago

@etshy We'll need more information to understand what to look for. Can you share with us which exact URL you are seeing this on (as example) and what the error is? In the screenshot, the error code is at the bottom and said ERR_CONNECTION_CLOSED. Do you see the same error code?

Also, it would help to know which country you are connecting from. If you prefer to share this privately, you may share it by email with us at infrastructure-team@jquery.com and be sure to mention this GitHub issue.

Also knowing which local CDN node you are reouted to would help narrow down or confirm the cause of the issue. This requires some interaction with the Terminal (command prompt). If you can do that, that would help. Run these three commands:

dig code.jquery.com

dig AAAA code.jquery.com

curl -vvv -I https://code.jquery.com

For the dig commands, it is the ANSWER SECTION we are interested in. For the curl command, it is the early Connected to […] line and the late x-hw: […] response header that is of interest (or if these aren't sent, then whatever the error is that was encountered).