Do not add PageParserPaths to web.config |
PageParserPaths can be used to enable inline code in ASPX pages which is not allowed.
| CheckId | SPC020210 |
|---|---|
| TypeName | DoNotAddPageParserPathToWebConfig |
| Severity | CriticalWarning |
| Type | Assembly |
Do not add PageParserPaths to web.config via SPWebConfigModification to enable inline code in ASPX pages.
The rule can only check the appearance of 'SPWebConfigModification' and the string 'PageParserPaths' in the same class. This can lead to false positive results.
To suppress this violation in managed code add the following attribute to the method which contains the instruction (available since SPCAF version v5.2). Learn more about SuppressMessage here.
// Important: Ensure to have #define CODE_ANALYSIS at the beginning of your .cs file
[SuppressMessage("SPCAF.Rules.SecurityGroup", "SPC020210:DoNotAddPageParserPathToWebConfig", Justification = "Provide reason for suppression here")]
[SuppressMessage("SPCAF.Rules.SecurityGroup", "SPC020210:DoNotAddPageParserPathToWebConfig", Justification = "Provide reason for suppression here")]
Disclaimer: The views and opinions expressed in this documentation and in SPCAF do not necessarily reflect the opinions and recommendations of Microsoft or any member of Microsoft. SPCAF and RENCORE are registered trademarks of Rencore. All other trademarks, service marks, collective marks, copyrights, registered names, and marks used or cited by this documentation are the property of their respective owners.