<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Url-Encoding on NavProject Blog</title>
    <link>https://navshelf.com/en/tags/url-encoding/</link>
    <description>Recent content in Url-Encoding on NavProject Blog</description>
    <generator>Hugo</generator>
    <language>en</language>
    <lastBuildDate>Sat, 12 Sep 2026 11:00:00 +0800</lastBuildDate>
    <atom:link href="https://navshelf.com/en/tags/url-encoding/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Base64 vs URL Encoding: What&#39;s the Difference and When to Use Each</title>
      <link>https://navshelf.com/en/posts/base64-vs-url-encoding/</link>
      <pubDate>Sat, 12 Sep 2026 11:00:00 +0800</pubDate>
      <guid>https://navshelf.com/en/posts/base64-vs-url-encoding/</guid>
      <description>Base64 and percent-encoding both turn data into safe text, but they solve different problems. Here is how to tell them apart, with examples and the mistakes each one causes.</description>
    </item>
    <item>
      <title>URL Encoding Explained: How to Encode Query Parameters Correctly</title>
      <link>https://navshelf.com/en/posts/url-encoding-explained/</link>
      <pubDate>Thu, 10 Sep 2026 10:00:00 +0800</pubDate>
      <guid>https://navshelf.com/en/posts/url-encoding-explained/</guid>
      <description>A practical guide to URL encoding (percent-encoding): which characters must be escaped, the difference between encodeURI and encodeURIComponent, why decoding fails, and a free browser-based encoder.</description>
    </item>
  </channel>
</rss>
