1 Risposta
- Più recenti
- Maggior numero di voti
- Maggior numero di commenti
1
Sorry to hear about the issues you are having. The AWS WAF CrossSiteScripting_BODY rule is sensitive to files with random characters in their metadata. The first step is to turn on comprehensive logs and look at the termindateRuleMatchDetails data.
Use the matchData field in the termindateRuleMatchDetails data to create a safe list with a match condition. There is a detailed step by step description in this knowledge center article.
Let me know if you are still having issues or if you have any other questions.
con risposta 24 giorni fa
Contenuto pertinente
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 2 anni fa
- AWS UFFICIALEAggiornata 7 mesi fa
- AWS UFFICIALEAggiornata 2 anni fa
Thanks, I went with a IP whitelist for the specific endpoint. Not optimal, but good enough for now.