Re-add minecraft.txt for Minecraft

[some-username-here1]

What CDN does this PR relate to

A previously available CDN before it was deleted without a valid reasoning.

Does this require running via sniproxy

N/A (does it mean a "No" if you can download the files via http anyway?)

Capture method

Via the minecraft launcher log

Testing Scenario

Testing Configuration

<!-- Paste either your docker run command from the DNS container OR explain how you have setup DNS zone files etc to test this issue -->

[Lepidopterist]

Mionecraft is now https ( as per #45 ) and not cacheable. Please provide evidence this is incorrect, and we will update.

[some-username-here1]

Is this still appliable as evidence? (all being linked via http)

launchermeta.mojang.com

pre-1.6.json
1.9.json
1.13.1.json

launcher.mojang.com

client.jar (1.3.2)
client.jar (1.9)
client-1.7.xml is forced through https (and redirected from http), so sniproxy is required to be used here if possible

resources.download.minecraft.net

asset object 1
asset object 2
asset object 3
asset object 4
asset object 5
asset object 6

I've tested these through my web browser, being Firefox and Chromium, so I didn't mean to provide invalid evidence if it's handled a different way.
Also I couldn't test libraries.minecraft.net as that returned a 403 "Bad request." Error either way (http or https)

[some-username-here1]

Or is this all invalid with the Minecraft Launcher going through https?
since I do want to try to redirect https to http for this, when possible

[VibroAxe]

@some-username-here1 I'm happy to merge this, you've done a good investigative job. Thanks

Can you please mark this as ready for review so we can continue

[some-username-here1]

With libraries.minecraft.net and resources.minecraft.net (I don't remember what this was used for, but I'll look on that) being included? Though that can be tested and then the file can be changed on feedback with what's the log (and access log) is outputting...

[VibroAxe]

if libraries.minecraft at least returns 403 on http that means it's listening, we can merge it so you can test it properly with steamcache-dns, if it doesn't work I can revert it back

[some-username-here1]

Alright!

[VibroAxe]

@some-username-here1 let me know if you have any issues

[some-username-here1]

Since it's now been merged, is there a way to update my current containers so that the minecraft service can be added, or I don't need to?

[VibroAxe]

aye, restarting the containers should pull the latest list

[some-username-here1]

Should I be concerned that the access.log isn't outputting anything? with using tail -f, or should I just wait for a while for it to go into effect?

Note: Nevermind, I looked into the log for my steamcache-dns container and it's looping with UPSTREAMDNS not having a ; in-between the IPv4 Addresses, will update once that's fixed