-
Notifications
You must be signed in to change notification settings - Fork 138
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
full_bin_index.7dbe22a9 frequent loading failed #1418
Comments
Hey @hurrykee! 👋 Thanks for the report! I think we could definitely retry to fetch those resources if they failed to load at a minimum 👍 In terms of proxying, we use Cloudflare and here it responded with Could you run:
and share what you get for Regarding caching, this resource, |
Thanks for the reply:
|
Woo it looks like you're being routed to the LHR data center which is based in london! 🤯 That sounds like our main issue here. Thanks for the info! 😃
The fact that resources are fetched again means that you don't have them in your local cache. All resources have a Note that if your cache is used, the resources will still appear in the network tab of the devtools but it will be served from your cache. I think the issue here is that you can't even get it in the first place? |
The Although the webcontainer version is updated frequently, in the actual production environment, we expect more stability. So, why not package these resources into a project that uses webcontainers? This way, you can make full use of the local network and closer CDN nodes. Of course, hypothesis we can configuration customized proxy server in the SDK, we can choose a better quality and local conditions of CDN acceleration line. Compared to Cloudflare this speed will be faster, the failure rate will be lower. |
The visit area is outside the United States, such as the Chinese mainland, Vietnam, Malaysia.
full_bin_index.7dbe22a9
file is relatively large, in the loading process, very vulnerable to the impact of the network environment, resulting in loading failed.Or is there another better solution?
The text was updated successfully, but these errors were encountered: