ys2843 opened a new issue #18367:
URL: https://github.com/apache/incubator-mxnet/issues/18367


   ## Description
   In MXNet website, JQuery script is loaded from google CDN in `<head>`
   ```html
   <script 
src="https://ajax.googleapis.com/ajax/libs/jquery/3.3.1/jquery.min.js";></script>
   ```
   But this CDN is known banned in China, as you can see here:
   + [Similar Github issues on other 
website](https://github.com/kubeflow/website/issues/81)
   + [Things to Consider When Building a Website in 
China](https://www.labsterx.com/blog/things-to-consider-when-building-a-website-in-china-9-shtml/)
   + [Can webflow team replace “ajax.googleapis.com” with a reachable URL for 
China?](https://forum.webflow.com/t/can-webflow-team-replace-ajax-googleapis-com-with-a-reachable-url-for-china/29284)
   
   It not only blocks website from loading, but also breaks all the interaction 
on MXNet website. (e.g. dropdown, installation guide, search etc. )
   
   ### Error Message
   `ReferenceError: jQuery is not defined[Learn More]`
   
   ## Proposed solutions 
   We need to solve this problem so that users in China can visit MXNet website 
without any problem. Here are 3 solutions:
   + Use an alternative CDN as a backup, when google CDN fails load the 
resource from backup CDN , as discussed [in this 
question](https://stackoverflow.com/questions/1014203/best-way-to-use-googles-hosted-jquery-but-fall-back-to-my-hosted-library-on-go)(**Preferable**)
   + Replace google CDN by another CDN (**Not preferable**, google CDN works 
well in other countries only except China)
   + Hosting jQuery locally (**Not preferable** performance-wise, reasons can 
be found 
[here](https://meta.stackoverflow.com/questions/258288/use-of-ajax-googleapis-com-not-china-friendly)
 )
    


----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
[email protected]


Reply via email to