Download cache for Minecraft only available through the old launcher

[some-username-here1]

Describe the Issue(s) your having:

(workaround is included)

Minecraft is able to cache via the old minecraft launcher (< v2.0), which is good, but it's unable to work for the newer version of the launcher as it's forcing through https. The minecraft re-addition isn't as a downer as I thought it would've been when I first tested this and got nothing, but that you would have to move back to the old launcher to get it caching and working.

Describe your setup?

Using steamcache/steamcache-dns for the header, and steamcache/generic for the individual cache services

DNS Configuration:

docker run \
  --restart unless-stopped -d \
  --name steamcache-dns \
  -p 192.168.1.100:53:53/udp \
  -v /etc/localtime:/etc/localtime \
  -e WSUSCACHE_IP=192.168.1.100 \
  -e STEAMCACHE_IP=192.168.1.101 \
  -e NINTENDOCACHE_IP=192.168.1.102 \
  -e XBOXLIVECACHE_IP=192.168.1.103 \
  -e ORIGINCACHE_IP=192.168.1.104 \
  -e TWITCHCACHE_IP=192.168.1.105 \
  -e APPLECACHE_IP=192.168.1.106 \
  -e BLIZZARDCACHE_IP=192.168.1.107 \
  -e FRONTIERCACHE_IP=192.168.1.108 \
  -e RIOTCACHE_IP=192.168.1.109 \
  -e ARENANETCACHE_IP=192.168.1.110 \
  -e HIREZCACHE_IP=192.168.1.111 \
  -e SONYCACHE_IP=192.168.1.112 \
  -e ROCKSTARCACHE_IP=192.168.1.113 \
  -e UPLAYCACHE_IP=192.168.1.114 \
  -e NEXUSMODSCACHE_IP=192.168.1.115 \
  -e DAYBREAKCACHE_IP=192.168.1.116 \
  -e RENEGADEXCACHE_IP=192.168.1.117 \
  -e WARGAMINGCACHE_IP=192.168.1.118 \
  -e MINECRAFTCACHE_IP=192.168.1.119 \
  steamcache/steamcache-dns:latest

Are you running sniproxy?

Yes

Sniproxy output:

2019-02-17 11:41:25 recv(): Connection reset by peer, closing connection
2019-02-17 11:41:25 recv(): Connection reset by peer, closing connection
2019-02-17 11:41:25 recv(): Connection reset by peer, closing connection
2019-02-17 11:41:25 recv(): Connection reset by peer, closing connection
2019-02-17 11:42:45 recv(): Connection reset by peer, closing connection
2019-02-17 11:42:45 recv(): Connection reset by peer, closing connection
2019-02-17 11:42:45 recv(): Connection reset by peer, closing connection
2019-02-17 11:42:45 recv(): Connection reset by peer, closing connection
2019-02-17 11:46:32 recv(): Connection reset by peer, closing connection
2019-02-17 11:47:17 recv(): Connection reset by peer, closing connection
2019-02-17 11:47:17 recv(): Connection reset by peer, closing connection
2019-02-17 11:47:17 recv(): Connection reset by peer, closing connection
      1 2019-02-17 11:44:36 192.168.1.22:51140 -> 0.0.0.0:443 -> NONE [
      1 2019-02-17 12:04:10 192.168.1.22:52817 -> 0.0.0.0:443 -> NONE [
     29 launchermeta.mojang.com
     12 launcher.mojang.com
     34 libraries.minecraft.net
      3 resources.download.minecraft.net

[VibroAxe]

Is the newer launcher still working at least (albeit not through the cache)?

[VibroAxe]

@some-username-here1 This needs more investigation. Once we have the option to push branches/forks into the dns container you'll be able to test this properly and we can then properly consider a new PR

[some-username-here1]

Oh, yeah the new launcher still works, even if it doesn't pick up on the cache, only the old launcher picks up on it.

And I was able to test it for a couple of times with both launchers

EDIT: Here's my access.log if it'll help out, everything but launchermeta.mojang.com (that was cached for the news slider thing on the new launcher) worked with the old launcher