fix for re-request expired resources causing infinite loop #4255
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Credit to @AndyMoreland for figuring the problem out (see discussion on #3944).
setTimeout has a maximum value of 2147483647 (32bit integer) for all browsers. If set higher than that, the timeout is immediately fired.
For a tile with an expiry longer than ~24 days, like a tile with a
max-age=2592000
Cache-Control header (30 days),tileExpires - new Date().getTime()
> 2147483647, and you end up in an infinite tile fetch loop.Fortunately the browser knows the tile hasn't expired so it feeds GL JS from the browser cache and doesn't pound the tile server. But it does pound the browser pretty hard.