Minecraft Snapshot 13w17a does not use standard java proxy configurations
When launching MinecraftDev.jar with the following command.
java -Dhttp.proxyHost=[host] -Dhttp.proxyPort=3128 -Dhttps.proxyHost=[host] -Dhttps.proxyPort=3128 -Xmx1024m -jar MinecraftDev.jar
The launcher attempts to the connect to the internet directly while trying to download the minecraft data rather than use the specified proxies. In the old launcher, it would use the specified proxy information.
I've tried exporting the following command as well with the same results.
export _JAVA_OPTIONS='-Dhttp.proxyHost=[host] -Dhttp.proxyPort=3128 -Dhttps.proxyHost=[host] -Dhttps.proxyPort=3128'
This is probably a relatively low impact bug, but impacts users who prefer to not have a default route to the internet and force all traffic through a proxy.
Environment
Debian Linux 6.0.7 Kernel 3.2 64bit JRE1.7
Linked Issues
Created Issue:
Minecraft Snapshot 13w17a does not use standard java proxy configurations
When launching MinecraftDev.jar with the following command.
java -Dhttp.proxyHost=[host] -Dhttp.proxyPort=3128 -Dhttps.proxyHost=[host] -Dhttps.proxyPort=3128 -Xmx1024m -jar MinecraftDev.jar
The launcher attempts to the connect to the internet directly while trying to download the minecraft data rather than use the specified proxies. In the old launcher, it would use the specified proxy information.
I've tried exporting the following command as well with the same results.
export _JAVA_OPTIONS='-Dhttp.proxyHost=[host] -Dhttp.proxyPort=3128 -Dhttps.proxyHost=[host] -Dhttps.proxyPort=3128'
This is probably a relatively low impact bug, but impacts users who prefer to not have a default route to the internet and force all traffic through a proxy.
Environment
Debian Linux 6.0.7 Kernel 3.2 64bit JRE1.7
MC-14752 → 
MCL-134![[Mojang] Grum (Erik Broes)](../../../data/assets/gravatar/grum.png){kind=small}
is duplicated by
is duplicated by
duplicates
is duplicated by
![[Mod] Ezekiel (ezfe)](../../../data/assets/gravatar/ezekielelin.jpeg){kind=small}
--proxyUser, --proxyPass, --proxyHost, --proxyPort.
Makes sense. Are those passed to minecraftdev.jar or instead of the standard proxy setting for Java? I'm guessing you mean to pass them to the launcher. I'll test when I am back in that environment.
To the jar or app or exe, all work. Giving it more memory doesn't work however.
That worked perfectly. Thank you for the clarification. I still pass the proxy info to java in the event that there is something else that requires that info.
There is no need to, we create a proxy object and pass it around throughout the code, I rather have you find something where we failed to do that than 'masking' it by adding these properties
Resolving all proxy related tickets to
MCL-102