Fix the formatting of the Note about REMOTE_USER and make it use @streq instead of a regexp

Flameeyes
2013-03-14 09:07:08 -07:00
parent af6e47c8fe
commit 6e13eac378

@@ -2021,10 +2021,9 @@ In the following example, we are evaluating to see whether the REMOTE_PORT is le
== REMOTE_USER == == REMOTE_USER ==
This variable holds the username of the authenticated user. If there are no password access controls in place (Basic or Digest authentication), then this variable will be empty. This variable holds the username of the authenticated user. If there are no password access controls in place (Basic or Digest authentication), then this variable will be empty.
<code>SecRule REMOTE_USER "^admin$" "id:38"</code> <code>SecRule REMOTE_USER "@streq admin" "id:38"</code>
; Note : In a reverse-proxy deployment, this information will not be available if the authentication is ; Note : In a reverse-proxy deployment, this information will not be available if the authentication is handled in the backend web server.
handled in the backend web server.
== REQBODY_ERROR == == REQBODY_ERROR ==
Contains the status of the request body processor used for request body parsing. The values can be 0 (no error) or 1 (error). This variable will be set by request body processors (typically the multipart/request-data parser or the XML parser) when they fail to do their work. Contains the status of the request body processor used for request body parsing. The values can be 0 (no error) or 1 (error). This variable will be set by request body processors (typically the multipart/request-data parser or the XML parser) when they fail to do their work.