@@ -188,7 +188,7 @@ Transaction::~Transaction() {
188188 *
189189 * Debug logs are important during the rules creation phase, this method can be
190190 * used to print message on this debug log.
191- *
191+ *
192192 * @param level Debug level, current supported from 0 to 9.
193193 * @param message Message to be logged.
194194 *
@@ -665,7 +665,7 @@ int Transaction::addRequestHeader(const unsigned char *key, size_t key_n,
665665 * @note It is necessary to "append" the request body prior to the execution
666666 * of this function.
667667 * @note Remember to check for a possible intervention.
668- *
668+ *
669669 * @returns If the operation was successful or not.
670670 * @retval true Operation was successful.
671671 * @retval false Operation failed.
@@ -685,11 +685,11 @@ int Transaction::processRequestBody() {
685685
686686 /*
687687 * Process the request body even if there is nothing to be done.
688- *
688+ *
689689 * if (m_requestBody.tellp() <= 0) {
690690 * return true;
691691 * }
692- *
692+ *
693693 */
694694 std::unique_ptr<std::string> a = m_variableRequestHeaders.resolveFirst (
695695 " Content-Type" );
@@ -878,7 +878,7 @@ int Transaction::processRequestBody() {
878878 *
879879 * With this method it is possible to feed ModSecurity with data for
880880 * inspection regarding the request body. There are two possibilities here:
881- *
881+ *
882882 * 1 - Adds the buffer in a row;
883883 * 2 - Adds it in chunks;
884884 *
@@ -983,7 +983,7 @@ int Transaction::appendRequestBody(const unsigned char *buf, size_t len) {
983983 *
984984 * @param code The returned http code.
985985 * @param proto Protocol used on the response.
986- *
986+ *
987987 * @returns If the operation was successful or not.
988988 * @retval true Operation was successful.
989989 * @retval false Operation failed.
@@ -1079,7 +1079,7 @@ int Transaction::addResponseHeader(const unsigned char *key,
10791079 * @param key_n header name size.
10801080 * @param value header value.
10811081 * @param value_n header value size.
1082- *
1082+ *
10831083 * @returns If the operation was successful or not.
10841084 * @retval true Operation was successful.
10851085 * @retval false Operation failed.
@@ -1164,7 +1164,7 @@ int Transaction::processResponseBody() {
11641164 * With this method it is possible to feed ModSecurity with data for
11651165 * inspection regarding the response body. ModSecurity can also update the
11661166 * contents of the response body, this is not quite ready yet on this version
1167- * of the API.
1167+ * of the API.
11681168 *
11691169 * @note If the content is updated, the client cannot receive the content
11701170 * length header filled, at least not with the old values. Otherwise
@@ -1312,7 +1312,7 @@ int Transaction::processLogging() {
13121312 this ->m_rules ->evaluate (modsecurity::LoggingPhase, this );
13131313
13141314 /* If relevant, save this transaction information at the audit_logs */
1315- if (m_rules != NULL && m_rules ->m_auditLog != NULL ) {
1315+ if (m_rules->m_auditLog != NULL ) {
13161316 int parts = this ->m_rules ->m_auditLog ->getParts ();
13171317 ms_dbg (8 , " Checking if this request is suitable to be " \
13181318 " saved as an audit log." );
@@ -1352,7 +1352,7 @@ int Transaction::processLogging() {
13521352 * @brief Check if ModSecurity has anything to ask to the server.
13531353 *
13541354 * Intervention can generate a log event and/or perform a disruptive action.
1355- *
1355+ *
13561356 * If the return value is true, all fields in the ModSecurityIntervention
13571357 * parameter have been initialized and are safe to access.
13581358 * If the return value is false, no changes to the ModSecurityIntervention
@@ -1801,7 +1801,7 @@ int Transaction::updateStatusCode(int code) {
18011801 *
18021802 * The transaction is the unit that will be used the inspect every request. It holds
18031803 * all the information for a given request.
1804- *
1804+ *
18051805 * @note Remember to cleanup the transaction when the transaction is complete.
18061806 *
18071807 * @param ms ModSecurity core pointer.
@@ -1913,7 +1913,7 @@ extern "C" int msc_process_request_headers(Transaction *transaction) {
19131913 * @note Remember to check for a possible intervention.
19141914 *
19151915 * @param transaction ModSecurity transaction.
1916- *
1916+ *
19171917 * @returns If the operation was successful or not.
19181918 * @retval 1 Operation was successful.
19191919 * @retval 0 Operation failed.
@@ -1930,7 +1930,7 @@ extern "C" int msc_process_request_body(Transaction *transaction) {
19301930 *
19311931 * With this function it is possible to feed ModSecurity with data for
19321932 * inspection regarding the request body. There are two possibilities here:
1933- *
1933+ *
19341934 * 1 - Adds the buffer in a row;
19351935 * 2 - Adds it in chunks;
19361936 *
@@ -1944,7 +1944,7 @@ extern "C" int msc_process_request_body(Transaction *transaction) {
19441944 * in this case is upon the rules.
19451945 *
19461946 * @param transaction ModSecurity transaction.
1947- *
1947+ *
19481948 * @returns If the operation was successful or not.
19491949 * @retval 1 Operation was successful.
19501950 * @retval 0 Operation failed.
@@ -2015,7 +2015,7 @@ extern "C" int msc_process_response_body(Transaction *transaction) {
20152015 * With this function it is possible to feed ModSecurity with data for
20162016 * inspection regarding the response body. ModSecurity can also update the
20172017 * contents of the response body, this is not quite ready yet on this version
2018- * of the API.
2018+ * of the API.
20192019 *
20202020 * @note If the content is updated, the client cannot receive the content
20212021 * length header filled, at least not with the old values. Otherwise
@@ -2122,7 +2122,7 @@ extern "C" int msc_add_response_header(Transaction *transaction,
21222122 * @param key_len header name size.
21232123 * @param value header value.
21242124 * @param val_len header value size.
2125- *
2125+ *
21262126 * @returns If the operation was successful or not.
21272127 * @retval 1 Operation was successful.
21282128 * @retval 0 Operation failed.
0 commit comments