github_mirrors/ModSecurity
3
0
Fork 1
mirror of https://github.com/owasp-modsecurity/ModSecurity.git synced 2025-08-14 05:45:59 +03:00
Code Issues Packages Projects Releases Wiki Activity

Document MULTIPART_CRLF_LF_LINES.

Browse Source
This commit is contained in:
ivanr 2007-10-15 18:27:42 +00:00
parent b0d514478f
commit f66e8c5b38
1 changed files with 19 additions and 1 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

20
doc/modsecurity2-apache-reference.xml
View File

@ -3,7 +3,7 @@
<title>ModSecurity Reference Manual</title>
<articleinfo>
<releaseinfo>Version 2.5.0-dev3 / (October 1, 2007)</releaseinfo>
<releaseinfo>Version 2.5.0-dev?/ (October 15, 2007)</releaseinfo>
<copyright>
<year>2004-2007</year>
@ -2332,6 +2332,24 @@ SecRule <emphasis role="bold">TX:MYMATCH</emphasis> "@eq ARGS:param" deny</progr
SecRule ARGS "@pm some key words" deny,status:500</programlisting>
</section>
<section>
<title><literal>MULTIPART_CRLF_LF_LINES</literal></title>
<para>This flag variable will be set to <literal>1</literal> whenever a
multipart request uses mixed line terminators. The
<literal>multipart/form-data</literal> RFC requires
<literal>CRLF</literal> sequence to be used to terminate lines. Since
some client implementations use only <literal>LF</literal> to terminate
lines you might want to allow them to proceed under certain
circumstances (if you want to do this you will need to stop using
<literal>MULTIPART_STRICT_ERROR</literal> and check each multipart flag
variable individually, avoding <literal>MULTIPART_LF_LINE</literal>).
However, mixing <literal>CRLF</literal> and <literal>LF</literal> line
terminators is dangerous as it can allow for evasion. Therefore, in such
cases, you will have to add a check for
<literal>MULTIPART_CRLF_LF_LINES</literal>. </para>
</section>
<section>
<title><literal>MULTIPART_STRICT_ERROR</literal></title>