-
-
Notifications
You must be signed in to change notification settings - Fork 334
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
Improve Cloudfront config #1081
Comments
|
I'll keep this issue open to do some related stuff though:
|
Ha, that was quick fixing! Good work. |
It's been stressing me out for a few days, but I just now had time to look into it... |
https://play.abstreet.org/0.3.43/ltn.html?system/gb/bristol/maps/east.bin already works. For some unknown reason, I've just been copying http:https:// links everywhere. Fixing now. |
I just enabled HTTPS forwarding for all subdomains of abstreet.org in Google Domains, so will update more links accordingly |
Broken: http:https://play.abstreet.org/0.3.43/santa.html
Working: http:https://abstreet.s3-website.us-east-2.amazonaws.com/0.3.43/santa.html
The network tab doesn't even show a .wasm file being loaded:
![Screenshot from 2023-04-20 19-31-05](https://user-images.githubusercontent.com/1664407/233456126-20761203-03c8-4e4d-b55c-c2c735af706f.png)
This appears to have quietly broken a week or two ago, despite there being no recent changes anywhere (S3 or Cloudfront activity generally). I invalidated the entire Cloudfront cache to be safe, but no effect.
IIUC, it looks like Cloudfront stopped returning
Content-Length
headers? We try to grab that before streaming data back:abstreet/web/src/widgetry.ts
Line 121 in 4314a43
@michaelkirk if you happen to have any ideas what could've broken, I'd welcome some help! But no pressure, I'm comfortable enough in TS to figure this out now. :)
The text was updated successfully, but these errors were encountered: