petsoi@discuss.tchncs.de to Linux@lemmy.ml · 3 months agoSwitch to Container Tabs – These Weeks in Firefox: Issue 157blog.nightly.mozilla.orgexternal-linkmessage-square15fedilinkarrow-up177arrow-down11cross-posted to: firefox@lemmy.ml
arrow-up176arrow-down1external-linkSwitch to Container Tabs – These Weeks in Firefox: Issue 157blog.nightly.mozilla.orgpetsoi@discuss.tchncs.de to Linux@lemmy.ml · 3 months agomessage-square15fedilinkcross-posted to: firefox@lemmy.ml
minus-squarecatloaf@lemm.eelinkfedilinkEnglisharrow-up14arrow-down5·3 months agoThat’s good, but out of scope for a browser, really. Also there shouldn’t be passwords in URLs!
minus-squarePlusMinus@lemmy.worldlinkfedilinkarrow-up19·3 months agoIt is not out ot scope. Basic auth exists: https://username:password@example.com
minus-square____@infosec.publinkfedilinkarrow-up2·3 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-squarecatloaf@lemm.eelinkfedilinkEnglisharrow-up3arrow-down1·3 months agoI forgot about that. It shouldn’t, these days.
minus-squarebmarinov@lemmy.worldlinkfedilinkarrow-up1·3 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: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.