From 50b51cb3f1d4bc2387b32c8190c89907e99113ad Mon Sep 17 00:00:00 2001
From: "xuanyi.wang" <xuanyi.wang@gtsplab.com>
Date: Thu, 25 May 2023 17:44:51 +0200
Subject: [PATCH] Update page 'OWASP test - Sloetjes'

---
 OWASP test - Sloetjes.md | 1 -
 1 file changed, 1 deletion(-)

diff --git a/OWASP test - Sloetjes.md b/OWASP test - Sloetjes.md
index 5d99fd1..2e79141 100644
--- a/OWASP test - Sloetjes.md	
+++ b/OWASP test - Sloetjes.md	
@@ -141,7 +141,6 @@
 * List three things to look for in an input sanitizer to avoid XSS problems.
 > Input sanitizers should:
 
-
     > Be context-aware: Different contexts (like HTML, URLs, CSS, or JavaScript) have different rules about what characters are dangerous.
     > Encode or remove special characters: Characters like <, >, ", ', and & often need to be encoded depending on context.
     > Be regularly updated and maintained: New attack techniques are discovered regularly, and a good sanitizer library will keep up with these techniques.
\ No newline at end of file