From acbe33a4a697a37af2461ac7b8786ef17fce21eb Mon Sep 17 00:00:00 2001 From: Felipe Zipitria Date: Mon, 26 Oct 2026 10:44:28 -0300 Subject: [PATCH] Replace dead SpiderLabs link in base64DecodeExt with archived copy The SpiderLabs blog post on Base64 impedance mismatch is offline. Point to the Internet Archive snapshot instead. Reported-by: MefhigosetH Co-Authored-By: Claude Opus 5.5 Claude-Session: https://claude.ai/code/session_01RiUJuqXNvvpytiGRiDFyTy --- content/3-reference-manual/3-4-transformation-functions.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/3-reference-manual/3-4-transformation-functions.md b/content/3-reference-manual/3-4-transformation-functions.md index 160f9de..f3730da 100644 --- a/content/3-reference-manual/3-4-transformation-functions.md +++ b/content/3-reference-manual/3-4-transformation-functions.md @@ -74,7 +74,7 @@ Decodes a Base64-encoded string. Unlike base64Decode, this version uses a more f Both engines accept the URL-safe alphabet (`-` and `_`) since ModSecurity 2.9.15 and libModSecurity 3.0.17. ModSecurity v2 skips only space, tab, CR, LF and padding (`=`) characters: any other byte outside the Base64 alphabet makes the whole decode fail and the output is an empty string. It also stops decoding at the first NUL byte in the input. libModSecurity v3 skips every byte outside the alphabet and processes every byte. -See blog post on Base64Decoding evasion issues on PHP sites - +See the blog post on Base64 decoding evasion issues on PHP sites, [Impedance Mismatch and Base64](https://web.archive.org/web/20110713164920/http://blog.spiderlabs.com/2010/04/impedance-mismatch-and-base64.html) (Internet Archive copy; the original SpiderLabs blog is offline). ## base64Encode