Fix CDN split: use global CDN for fetch, regional CDN for install#110
Open
Smiie-2 wants to merge 1 commit into
Open
Fix CDN split: use global CDN for fetch, regional CDN for install#110Smiie-2 wants to merge 1 commit into
Smiie-2 wants to merge 1 commit into
Conversation
Regional CDNs (eu/us/kr.cdn.blizzard.com) only host game data files — config and metadata files return 404 from regional CDNs and must be fetched from the global level3.blizzard.com CDN. Split the ngdp calls so that: - fetch (config/metadata) uses the default global CDN - install (game data) uses the faster regional CDN Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Problem
Regional CDNs (
eu/us/kr.cdn.blizzard.com) only host game data files. Config and metadata files (build config, CDN config, archive indices) return HTTP 404 from regional CDNs.When
--cdnwas passed tongdp fetch, keg attempted to fetch config files from the regional CDN and failed withFileNotFoundErrorafter the 404.Fix
Split the two
ngdpcalls so each uses the appropriate CDN:ngdp fetch(config/metadata) — no--cdnoverride, uses the default globallevel3.blizzard.comngdp install(game data) — uses--cdnwith the faster regional CDNTesting
Verified on EU region — fresh install completes without 404 errors on config files, and game data downloads from the regional CDN.
🤖 Generated with Claude Code