this post was submitted on 02 Apr 2024
76 points (98.7% liked)

Linux

47224 readers
794 users here now

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word "Linux" in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] flashgnash@lemm.ee 8 points 5 months ago (1 children)

That just seems like crappy website design

[–] strcrssd@kbin.social 11 points 5 months ago (1 children)

It has nothing to do with website design. It's part of the HTTP protocol. A poor part in today's understanding and use cases, but in the 90s it would have made sense.

[–] flashgnash@lemm.ee 2 points 5 months ago (1 children)

We're both talking about route parameters right?

[–] Ghoelian@lemmy.dbzer0.com 6 points 5 months ago (1 children)

I think they're talking about basic Auth, with which you can pass credentials in a URL like this:

https://username:password@website.com

[–] flashgnash@lemm.ee 2 points 5 months ago (1 children)

I thought basic Auth was where you base64 encoded the username and password and sent it as the Authorization header

[–] Ghoelian@lemmy.dbzer0.com 3 points 5 months ago* (last edited 5 months ago)

That is also a form of basic auth, you still pass the credentials like "username:password", optionally base64 encoded but I don't believe that's required.

Edit: actually, after looking into it a bit more, it seems like passing credentials in the url will actually cause the browser to send it as an authorization header instead. So in essence it's doing the same thing.