LUA-URI-HTTP(3)

💖 NAME 💖

lua-uri-http — HTTP URI support for the Lua URI library 🦋

okay bestie, listen, this is the page about how the Lua URI library handles http and https links, and it's literally so straightforward, you're gonna eat this up 💅

---

✨ DESCRIPTION ✨

So the classes uri.http and uri.https are the ones you reach for when your URI has the http or https scheme respectively. Simple. Iconic. No notes. 👑

Here's the family tree, and the way it works is giving inheritance:

• uri.http inherits from the generic uri class 🌸
• uri.https inherits from uri.http 🎀

So yes, uri.https is lowkey the baby of uri.http, and uri.http is the main character.

🚩 Big red flag incoming: an HTTP or HTTPS URI that contains any userinfo part is considered to be invalid. Not "kinda sus", not "we'll allow it" — invalid, periodt. So don't put userinfo in there, bestie, it's not the vibe.

Also, an empty path gets normalized to / — because browsers usually do that anyway, and fr fr an empty path just cannot be used in an HTTP GET request. So the library is doing you a solid and fixing it for you. 🫶

Now the ports, and this part you should highkey memorize:

• default port for the http scheme is 80 ⭐
• default port for the https scheme is 443 🌈

And here's the part where the page says something a lil wild: there are no extra methods defined for telnet URIs — only those described in lua-uri(3). Yes, it says telnet, and I'm just relaying it exactly as it's written, no editing, no cap 🙈. If you want the methods, go read lua-uri(3), that's where they live.

---

📚 REFERENCES 📚

So, as far as the author can tell, there is no up to date specification of the syntax of HTTP URIs 😭 which is honestly so real of the internet. Because of that, this class is based on:

• RFC 1738 section 3.3
• RFC 2616 section 3.2.2

That's it, that's the whole sourcing situation. Historic, honestly. 💀

---

Version 1.1, dated 2012-00-00 — yeah bestie, this page is a vintage, it's giving classic, and it still slays. Bye, ily, go build some URIs 💜✨