This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde. (Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique. (Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica. (Aviso legal)
此内容已经过机器动态翻译。 放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다. 책임 부인
Este texto foi traduzido automaticamente. (Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt. (Haftungsausschluss)
Ce article a été traduit automatiquement. (Clause de non responsabilité)
Este artículo ha sido traducido automáticamente. (Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
XML content types
By default, the Web App Firewall treats files that follow certain naming conventions as XML. You can configure the Web App Firewall to examine web content for additional strings or patterns that indicate that those files are XML files. This can ensure that the Web App Firewall recognizes all XML content on your site, even if certain XML content does not follow normal XML naming conventions, ensuring that XML content is subjected to XML security checks.
To configure the XML content types, you add the appropriate patterns to the XML Content Types list. You can enter a content type as a string, or you can enter a PCRE-compatible regular expression specifying one or more strings. You can also modify the existing XML content types patterns.
To add an XML content type pattern by using the command line interface
At the command prompt, type the following commands:
add appfw XMLContentType <XMLContenttypevalue> [-isRegex ( REGEX | NOTREGEX )]
save ns config
Example
The following example adds the pattern .*/xml to the XML Content Types list and designates it as a regular expression.
add appfw XMLContentType ".*/xml" -isRegex REGEX
<!--NeedCopy-->
To remove an XML content type pattern by using the command line interface
At the command prompt, type the following commands:
rm appfw XMLContentType <XMLContenttypevalue>
save ns config
To configure the XML content type list by using the GUI
- Navigate to Security > Web App Firewall.
- In the details pane, under Settings, click Manage XML Content Types.
- In the Manage XML Content Types dialog box, do one of the following:
- To add a new XML content type, click Add.
- To modify an existing XML content type, select that type and then click Edit. The Configure Web App Firewall XML Content Type dialog appears. Note: If you select an existing XML content type pattern and then click Add, the dialog box displays the information for that XML content type pattern. You can modify that information to create your new XML content type pattern.
- In the dialog box, fill out the elements. They are:
- IsRegex. Select or clear to enable PCRE-format regular expressions in the form field name.
- XML Content Type Enter a literal string or PCRE-format regular expression that matches the XML content type pattern that you want to add.
- Click Create.
- To remove an XML content type pattern from the list, select it, then click Remove to remove it, and then click OK to confirm your choice.
- When you have finished adding and removing XML content type patterns, click Close.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.