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

level3.ssl.blizzard.com #149

Open
Magissia opened this issue Aug 13, 2019 · 6 comments
Open

level3.ssl.blizzard.com #149

Magissia opened this issue Aug 13, 2019 · 6 comments

Comments

@Magissia
Copy link

Hello, blizzard is now using another domain for (at least) Heroes of the Storm data.

Hearthstone data is still provided without SSL from level3 right now.

@nexusofdoom
Copy link
Collaborator

updates for my client is still pulling down from this domain
2019-08-14 07:32:16 10.0.4.65 10.0.4.29 > GET level3.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.1 - -
2019-08-14 07:32:16 10.0.4.36 10.0.4.65 < - - - HTTP/1.1 206 Partial Content
2019-08-14 07:32:16 10.0.4.29 10.0.4.65 < - - - HTTP/1.1 206 Partial Content
2019-08-14 07:32:16 10.0.4.65 10.0.4.30 > GET level3.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.1 - -
2019-08-14 07:32:16 10.0.4.65 10.0.4.37 > GET level3.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.1 - -
2019-08-14 07:32:16 137.221.64.4 10.0.4.26 < - - - HTTP/1.1 206 Partial Content
2019-08-14 07:32:16 10.0.4.26 8.249.5.254 > GET level3.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.0 - -
2019-08-14 07:32:16 10.0.4.65 10.0.4.34 > GET us.cdn.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.1 - -
2019-08-14 07:32:16 10.0.4.26 137.221.64.8 > GET us.cdn.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.0 - -
2019-08-14 07:32:16 10.0.4.26 8.252.112.254 > GET level3.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.0 - -
2019-08-14 07:32:16 10.0.4.26 67.26.227.254 > GET level3.blizzard.com /tpr/Hero-Live-a/data/e4/9a/e49aed9426c2c27ed87681bd1a5541e5 HTTP/1.0

@nexusofdoom
Copy link
Collaborator

@Magissia
Copy link
Author

Update was still pulled from level3.ssl.blizzard.com and bypassed lancache.

My dnsmasq config :

server=/dist.blizzard.com/127.0.0.1
server=/llnw.blizzard.com/127.0.0.1
server=/level3.blizzard.com/127.0.0.1
server=/dist.blizzard.com.edgesuite.net/127.0.0.1
server=/blzddist1-a.akamaihd.net/127.0.0.1
server=/blzddist1-b.akamaihd.net/127.0.0.1
server=/blzddist2-a.akamaihd.net/127.0.0.1
server=/blzddist2-b.akamaihd.net/127.0.0.1
server=/blzddist3-a.akamaihd.net/127.0.0.1
server=/blzddist3-b.akamaihd.net/127.0.0.1
server=/blizzard.vo.llnwd.net/127.0.0.1
server=/edge.blizzard.top.comcast.net/127.0.0.1
server=/edgecast.blizzard.com/127.0.0.1
#server=/nydus.battle.net/127.0.0.1
server=/.cdn.blizzard.com/127.0.0.1
server=/llnw.eu.blizzard.com/127.0.0.1
server=/llnw.us.blizzard.com/127.0.0.1
server=/blzddistkr1-a.akamaihd.net/127.0.0.1
server=/blizzard.nefficient.co.kr/127.0.0.1

And my hosts

192.168.170.1 dist.blizzard.com
192.168.170.1 llnw.blizzard.com
192.168.170.1 level3.blizzard.com
xxx::170:1 level3.blizard.com
192.168.170.1 dist.blizzard.com.edgesuite.net
192.168.170.1 blzddist1-a.akamaihd.net
192.168.170.1 blzddist1-b.akamaihd.net
192.168.170.1 blzddist2-a.akamaihd.net
192.168.170.1 blzddist2-b.akamaihd.net
192.168.170.1 blzddist3-a.akamaihd.net
192.168.170.1 blzddist3-b.akamaihd.net
192.168.170.1 blizzard.vo.llnwd.net
192.168.170.1 edge.blizzard.top.comcast.net
192.168.170.1 edgecast.blizzard.com
#192.168.170.1 nydus.battle.net
192.168.170.1 cdn.blizzard.com eu.cdn.blizzard.com
xxx::170:1 cdn.blizzard.com eu.cdn.blizzard.com
192.168.170.1 llnw.eu.blizzard.com
192.168.170.1 llnw.us.blizzard.com
192.168.170.1 blzddistkr1-a.akamaihd.net
192.168.170.1 blizzard.nefficient.co.kr

nginx listen for all of these, but the ssl domain is not listened by nginx, not redirected by dnsmasq as I based my config on this repository config files for domains.

I see these requests floating around
Aug 15 13:41:34 dnsmasq[6732]: 99 192.168.170.52/37492 query[A] level3.ssl.blizzard.com from 192.168.170.52

@nagilum99
Copy link
Contributor

If it pulls it via SSL, there's not much we could do.
Not sure if an SSL-unwrapper would help, aka doing a MITM "attack" to cache that.

@nexusofdoom
Copy link
Collaborator

I would make a ticket with Blizzard just like we have with origin.. and please post the ticket so we can all reply to it.

Thanks

@SurferLancelot
Copy link

This has broken wow for me

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

No branches or pull requests

4 participants