<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Url-Parsing on Pi Stack</title>
    <link>https://www.pistack.xyz/tags/url-parsing/</link>
    <description>Recent content in Url-Parsing on Pi Stack</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Sun, 21 Jun 2026 00:00:00 +0000</lastBuildDate>
    <atom:link href="https://www.pistack.xyz/tags/url-parsing/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Self-Hosted URL Parsing Libraries: Ada vs uriparser vs llhttp vs rust-url</title>
      <link>https://www.pistack.xyz/posts/2026-06-21-url-parsing-libraries-ada-uriparser-llhttp-rust-url/</link>
      <pubDate>Sun, 21 Jun 2026 00:00:00 +0000</pubDate>
      <guid>https://www.pistack.xyz/posts/2026-06-21-url-parsing-libraries-ada-uriparser-llhttp-rust-url/</guid>
      <description>&lt;h2 id=&#34;introduction&#34;&gt;Introduction&lt;/h2&gt;&#xA;&lt;p&gt;Every web application, API client, and HTTP server needs to parse URLs. Whether you are extracting query parameters, validating user input, or routing requests, a fast and standards-compliant URL parser is essential infrastructure. While it is tempting to roll your own regex-based parser, the URL specification (WHATWG URL Standard and RFC 3986) has enough edge cases to fill a book — percent-encoding, IPv6 literals, Unicode normalization, and relative resolution are just the beginning.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
