-
-
Notifications
You must be signed in to change notification settings - Fork 22
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
Steam appears to getting captured by SNI Proxy #4
Comments
I'm seeing some chunks downloaded via SNIProxy also, however this does not appear to be limited to Comcast URLs, e.g:
I also note the hostnames seen above apparently have optional https_support:
Interestingly enough, the steam client doesn't seem to switch completely over to https, and will happily download some chunks via http (and be cached), while simultaneously downloading other chunks over https. As a quick hack I just redirected the hostnames I saw in my logs to a closed port on localhost, and once the steam client tries and fails once via https it does seem to happily failover to cacheable http.
|
See lancachenet/monolithic#85 for updates on the new steam supported http failback system - this should resolve outstanding steam/https/comcast issues. Feel free to reopen if still having issues with the new one. |
It looks like SNIProxy is hitting a domain owned by Comcast for steam downloads. I suspect that Steam/Comcast have an agreement that allows Comcast to host a CDN for their clients for Steam downloads.
If I simply disable SNIProxy, however, the downloads get cached with Steamcache Generic as expected. Not really sure what to make of this or if this is requiring a pull request sent to UKLans to have this resolved.
Brief logs
The text was updated successfully, but these errors were encountered: