ip2unix | url | |
---|---|---|
2 | 14 | |
350 | 505 | |
0.3% | 0.8% | |
7.4 | 5.9 | |
18 days ago | about 1 month ago | |
C++ | HTML | |
GNU Lesser General Public License v3.0 only | GNU General Public License v3.0 or later |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
ip2unix
-
Support HTTP over Unix domain sockets
Another LD_PRELOAD based solution can be found here: https://github.com/nixcloud/ip2unix
I use it to run a number of services under systemd, and haven’t had any issues.
-
Torrent clients with a web interface that can listen on a Unix socket?
I’m not aware of any clients that will do the former, but if that’s what’s you’re looking for you could consider using ip2unix [https://github.com/nixcloud/ip2unix].
url
-
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
- I am looking to learn everything about URLs in Web Development
- There’s more than one way to write an IP address (2019)
-
Just fighting URLSearchParams and wonder if anyone uses iterators IRL and what I do miss
What's imho missing is a size or count method. The reason they don't have one yet is because it's not clear whether it should be all tuples, or all keys. Discussion
-
Open source sustainment and the future of Gitea
Well, [text](href) is just a lousy syntax. Quite apart from how easy it is to forget which way round it is, the way round that it is is syntactically inferior: the parentheses are URL code points <https://url.spec.whatwg.org/#url-code-points>, so URL encoding won’t percent-encode parentheses, so Markdown doesn’t actually support all valid URLs, leading to injection attacks if all you do is regular URL encoding, deliberate or accidental, and deciding where an href ends is troublesome and inconsistent, with some Markdown implementations terminating at any right parenthesis, and others trying to match parentheses as a heuristic that helps most cases. The other way round, with the href in square brackets, would have been better in this regard, as square brackets aren’t URL code points, and thus will be percent-encoded. But better still would have been to lean on angle brackets more, matching long-held custom and the other style of links Markdown already uses (just plain ). In my own lightweight markup language that I’ve been working on for a while and am now polishing up and implementing properly, I’m currently using [text ]. [text] is also quite tempting, with slightly different trade-offs.
(When I speak of the details of URL encoding and which characters get percent-encoded, these things weren’t quite so clearly-defined back in 2004 as they are now, but I believe it was all still true.)
-
A valid domain name (remove www)
>A domain is a non-empty ASCII string that identifies a realm within a network. [RFC1034]
>The example.com and example.com. domains are not equivalent and typically treated as distinct.
https://url.spec.whatwg.org/#concept-domain
What are some alternatives?
ctsTraffic - ctsTraffic is a highly scalable client/server networking tool giving detailed performance and reliability analytics
firewalker - Testing framework for Cloudflare Firewall rules
dns-lookup - 🌍 DNS hostname resolution CLI tool using BSD sockets
streams - Streams Standard
InitKit - Neo-InitWare is a modular, cross-platform reimplementation of the systemd init system. It is experimental.
dom - DOM Standard
chkservice - Systemd units manager with ncurses, terminal interface
boost_epoch - Proposal for an epoch-based organization of Boost libraries
spacesockets2 - SpaceSockets2 makes socket programming much easier for C++ developers.
minCurl - a thin helper to use curl more easily
amd-disable-c6 - Systemd service to automatically disable the C6 power saving state on AMD Zen (Ryzen / Epyc) processors
HTMLKit - An Objective-C framework for your everyday HTML needs.