Switch to Container Tabs – These Weeks in Firefox: Issue 157petsoi@discuss.tchncs.de to Linux@lemmy.ml – 76 points – 3 months agoblog.nightly.mozilla.org15Post a CommentPreviewYou are viewing a single commentView all commentsShow the parent commentIt is not out ot scope. Basic auth exists: https://username:password@example.comI have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny. I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…I forgot about that. It shouldn't, these days.It is one of the easier ways to globally configure git auth for private Go packages.
It is not out ot scope. Basic auth exists: https://username:password@example.comI have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny. I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…I forgot about that. It shouldn't, these days.It is one of the easier ways to globally configure git auth for private Go packages.
I have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny. I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…
I forgot about that. It shouldn't, these days.It is one of the easier ways to globally configure git auth for private Go packages.
It is not out ot scope. Basic auth exists: https://username:password@example.com
I have this exact use case on a work machine, because the proxy flat refuses to prompt for the login, just goes straight to deny.
I own neither the proxy, nor the steaming heap of code that lives behind it, and I’m grateful for that every single day…
I forgot about that. It shouldn't, these days.
It is one of the easier ways to globally configure git auth for private Go packages.