SaaSHub helps you find the best software and product alternatives Learn more →
Url Alternatives
Similar projects and alternatives to url
-
-
Stream
Stream - Scalable APIs for Chat, Feeds, Moderation, & Video. Stream helps developers build engaging apps that scale to millions with performant and flexible Chat, Feeds, Moderation, and Video APIs and SDKs powered by a global edge network and enterprise-grade infrastructure.
-
-
-
-
-
-
InfluxDB
InfluxDB – Built for High-Performance Time Series Workloads. InfluxDB 3 OSS is now GA. Transform, enrich, and act on time series data directly in the database. Automate critical tasks and eliminate the need to move data externally. Download now.
-
-
-
-
-
-
-
-
-
-
-
-
-
-
SaaSHub
SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives
url discussion
url reviews and mentions
-
The URL Space is Bigger than the Universe
For the past few years I’ve been trying to build an operating system that can do everything you expect an operating system to do while also encoding its entire state as a single URL. That way, we get a permanent link to every O/S state, achieving truly comprehensive deep linking.
-
Dotless Domains
But it does comply with WHATWG’s URL Standard, which obsoletes RFC 3986, providing something that’s actually robustly implementable. Some things do definitely try to follow RFC 3986 still, but I think it’s largely legacy stuff, and the URL Standard is more important these days.
https://url.spec.whatwg.org/#host-parsing, follow step seven.
- If it is worth keeping, save it in Markdown
-
Python grapples with Apple App Store rejections
A comment on the issue linked from the PR references https://url.spec.whatwg.org/#url-serializing as a rationale for why itms-services would normally not have the "//" and therefore needs the exception. However that spec says non-null, not non-empty, so it sounds like python's URL library is actually just wrong here in that it's treating an empty host the same as null.
-
Unveiling URI, URL, and URN
To add to the mess, the WHATWG now maintains a "URL" spec that covers URIs and declares URIs an outdated term for URLs: https://url.spec.whatwg.org/
So now we have a URL spec that says URI is an old term for URLs, and a URI spec that says that URL is just a term for a certain subset of URIs.
-
Cool URIs can be ugly
Semicolon (;) has no special meaning in a URL. You can ascribe it a meaning in your particular routing, but the spec has nothing to say about it.
https://url.spec.whatwg.org/
- People like me are why you shouldn't run a hosting company
-
Support HTTP over Unix domain sockets
https://github.com/whatwg/url/issues/577#issuecomment-118534...
It's not insurmountable absolutely and I would appreciate it absolutely.
-
URL Explained – The Fundamentals
For the query portion, it really depends if your are reading it server side or client side and using the WHATWG standard[0] which itself just mirrors convention. However, the standard dictating how a URL might be formed does not mandate anything about the query string that makes it parsable.
0]: https://url.spec.whatwg.org/#interface-urlsearchparams
-
When URL parsers disagree (CVE-2023-38633, librsvg)
Browsers have discrepancies too of course. Here's an interesting Chromium bug I've been following: https://bugs.chromium.org/p/chromium/issues/detail?id=125253... and an associated WHATWG discussion: https://github.com/whatwg/url/issues/606
Some multiple examples of browsers disagreeing: https://www.yagiz.co/url-parsing-and-browser-differences
-
A note from our sponsor - SaaSHub
www.saashub.com | 19 Jul 2025
Stats
whatwg/url is an open source project licensed under GNU General Public License v3.0 or later which is an OSI approved license.
The primary programming language of url is HTML.