Hugo • 12/27/2024

URLs and percent encoding

Read Original

The article details a developer's realization that automatically decoding percent-encoded URLs in a library (libdav) is flawed. Using examples like '/path/to/theitem%2Fwithslash.ics', it explains how decoding reserved characters like '/' changes the resource's meaning. It references RFC3986 to distinguish between reserved and unreserved characters and advises treating URL paths as opaque strings for safety, with normalization only for comparison.

0 comments
#Uri #URL Encoding #Webdav
URLs and percent encoding

Comments

No comments yet

Be the first to share your thoughts!

Browser Extension

Get instant access to AllDevBlogs from your browser

Top of the Week

1
React vs Browser APIs (Mental Model)
Jivbcoop • 3 votes
2
React, useEffect, and Stale Closures: How to Avoid Them with Dependencies and useRef
Jivbcoop • 2 votes
3
Building Type-Safe Compound Components
TkDodo Dominik Dorfmeister • 2 votes
4
Using Browser Apis In React Practical Guide
Jivbcoop • 1 votes
5
Better react-hook-form Smart Form Components
Maarten Hus • 1 votes
6
Introducing RSC Explorer
Dan Abramov • 1 votes
7
The Pulse: Cloudflare’s latest outage proves dangers of global configuration changes (again)
The Pragmatic Engineer Gergely Orosz • 1 votes