@[email protected] to [email protected] • 9 months agoSwitch to Container Tabs – These Weeks in Firefox: Issue 157blog.nightly.mozilla.orgexternal-linkmessage-square15fedilinkarrow-up170arrow-down11cross-posted to: [email protected]
arrow-up169arrow-down1external-linkSwitch to Container Tabs – These Weeks in Firefox: Issue 157blog.nightly.mozilla.org@[email protected] to [email protected] • 9 months agomessage-square15fedilinkcross-posted to: [email protected]
minus-square@[email protected]linkfedilinkEnglish9•9 months agoThat’s good, but out of scope for a browser, really. Also there shouldn’t be passwords in URLs!
minus-square@PlusMinuslink18•9 months agoIt is not out ot scope. Basic auth exists: https://username:[email protected]
minus-square@[email protected]linkfedilink2•9 months agoI 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…
minus-square@[email protected]linkfedilinkEnglish1•9 months agoI forgot about that. It shouldn’t, these days.
minus-square@bmarinovlink1•9 months agoIt is one of the easier ways to globally configure git auth for private Go packages.
That’s good, but out of scope for a browser, really. Also there shouldn’t be passwords in URLs!
It is not out ot scope. Basic auth exists: https://username:[email protected]
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.