Skip to content
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

Add comcast domain #19

Merged
merged 1 commit into from
Aug 15, 2018
Merged

Add comcast domain #19

merged 1 commit into from
Aug 15, 2018

Conversation

JasonRivers
Copy link
Contributor

Comcast run a steam CDN, We have people in the US complaining that the cache isn't being hit on Comcast networks.

@VibroAxe
Copy link
Member

I wonder what comcast/steam are doing to intercept the request, and if there's anyway we could leverage this

@JasonRivers
Copy link
Contributor Author

Well, As far as I'm aware, Comcast do some very nasty things with intercepting data (though not as bad as Verizon), What I do know is that they have an agreement with Valve.

The more interesting bit is that Steam itself is requesting that domain, so steam knows it's on a Comcast network. This makes me wonder if Steam sends a message at startup or periodically saying "I'm here, what servers should I download from", if that's a remote request then either Comcast can intercept that and give it's own server, or, Valve respond giving the Comcast domain because they know it's on the Comcast network.

If we were able to intercept this in the same way, that would greatly reduce the DNS complexity for the caching server, I noticed that the Blizzard file has the same, too. Perhaps this might be a good addition to the RFC?

@sirsquidness
Copy link

sirsquidness commented Aug 15, 2018 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

7 participants