MCL-4869Document that launcher (and minecraft) is unable to use http(s) proxy
You have closed MCL-102 in 2013, still the net is full with failing advices and miscommunication. I was searching for the answer for weeks, found nothing. Eventually I came here to report the bug and search revealed MCL-102 which basically states that - contrary to popular belief - minecraft cannot use http proxy, no workaround and no hack, and if someone requires it then they should not buy minecraft since it will not work. (sidenote: In Linux environment plenty of people are using squid http proxies and firewall outbound crap as a local policy. I have never seen anyone providing socksX proxies by default.)
Having said that you have commented in 2013 that you should have this documented. INDEED YOU SHOULD. Please. Write in the help, in the faq, enter it into the launcher documentation and save frustrated hours of trying. Pretty please. I am quite annoyed, but that's my personal problem, but it's your problem to save the future others from getting this bad vibe again and again. Be nice, if you cannot program it then at least document this issue.
Thank you.
Created Issue:
Document that launcher (and minecraft) is unable to use http(s) proxy
You have closed
MCL-102in 2013, still the net is full with failing advices and miscommunication. I was searching for the answer for weeks, found nothing. Eventually I came here to report the bug and search revealedMCL-102which basically states that - contrary to popular belief - minecraft cannot use http proxy, no workaround and no hack, and if someone requires it then they should not buy minecraft since it will not work. (sidenote: In Linux environment plenty of people are using squid http proxies and firewall outbound crap as a local policy. I have never seen anyone providing socksX proxies by default.)Having said that you have commented in 2013 that you should have this documented. INDEED YOU SHOULD. Please. Write in the help, in the faq, enter it into the launcher documentation and save frustrated hours of trying. Pretty please. I am quite annoyed, but that's my personal problem, but it's your problem to save the future others from getting this bad vibe again and again. Be nice, if you cannot program it then at least document this issue.
Thank you.
Would you please care to share as how is this issue invalid?
Is it documented anywhere officially that http/s proxies are not supported, so my request was beating a dead horse?
Or are they supported, and I have been mistaken, but then again, I was absolutely unable to get it working (along with everyone else)?
Or you're just lazy to document a deficiency in the program along with the fact that you're not fixing it, to make the life of plenty of people harder, and saying "invalid" seems like a good catch-all to prevent the need of explaining?
Also "[Mojang] Grum (Erik Broes)" said in 2013 that this should be documented. Was it documented? If not, it doesn't seem very invalid to me.
What you reported is a feature/change request, not a bug, that's why it's resolved as invalid, not a bug, not supposed to be on this site.