Hi,

This patch fixes typos in the code comments of the proto_http
subsystem using misspell, same as previous patches.

The patch is attached, but if you want to view the diff online, you
can check: 
https://github.com/haproxy/haproxy/compare/master...aerostitch:cleanup_proto_http_typos

Thanks,
Joseph
From 9062ff3570766836b53fe00ca9821003535fced5 Mon Sep 17 00:00:00 2001
From: Joseph Herlant <aerosti...@debian.org>
Date: Thu, 15 Nov 2018 09:25:36 -0800
Subject: [PATCH] CLEANUP: fix typos in the proto_http subsystem

Fixes typos in the code comments of the proto_http subsystem.
---
 include/types/proto_http.h |  8 ++++----
 src/proto_http.c           | 10 +++++-----
 2 files changed, 9 insertions(+), 9 deletions(-)

diff --git a/include/types/proto_http.h b/include/types/proto_http.h
index 1b10c079..0f341e2e 100644
--- a/include/types/proto_http.h
+++ b/include/types/proto_http.h
@@ -187,11 +187,11 @@ enum {
 	STAT_STATUS_INIT = 0,
 	STAT_STATUS_DENY,	/* action denied */
 	STAT_STATUS_DONE,	/* the action is successful */
-	STAT_STATUS_ERRP,	/* an error occured due to invalid values in parameters */
-	STAT_STATUS_EXCD,	/* an error occured because the buffer couldn't store all data */
+	STAT_STATUS_ERRP,	/* an error occurred due to invalid values in parameters */
+	STAT_STATUS_EXCD,	/* an error occurred because the buffer couldn't store all data */
 	STAT_STATUS_NONE,	/* nothing happened (no action chosen or servers state didn't change) */
 	STAT_STATUS_PART,	/* the action is partially successful */
-	STAT_STATUS_UNKN,	/* an unknown error occured, shouldn't happen */
+	STAT_STATUS_UNKN,	/* an unknown error occurred, shouldn't happen */
 	STAT_STATUS_SIZE
 };
 
@@ -207,7 +207,7 @@ enum {
  *                             During parsing, it points to last header seen
  *                             for states after START. When in HTTP_MSG_BODY,
  *                             eoh points to the first byte of the last CRLF
- *                             preceeding data. Relative to buffer's origin.
+ *                             preceding data. Relative to buffer's origin.
  *                             This value then remains unchanged till the end
  *                             so that we can rewind the buffer to change some
  *                             headers if needed (eg: http-send-name-header).
diff --git a/src/proto_http.c b/src/proto_http.c
index c5d35437..cb015009 100644
--- a/src/proto_http.c
+++ b/src/proto_http.c
@@ -1199,7 +1199,7 @@ int http_wait_for_request(struct stream *s, struct channel *req, int an_bit)
 			}
 		}
 
-		/* nothing to fail, let's reply normaly */
+		/* nothing to fail, let's reply normally */
 		txn->status = 200;
 		http_reply_and_close(s, txn->status, http_error_message(s));
 		if (!(s->flags & SF_ERR_MASK))
@@ -2122,7 +2122,7 @@ resume_execution:
 			}
 			break;
 
-		/* other flags exists, but normaly, they never be matched. */
+		/* other flags exists, but normally, they never be matched. */
 		default:
 			break;
 		}
@@ -2477,7 +2477,7 @@ resume_execution:
 			}
 			break;
 
-		/* other flags exists, but normaly, they never be matched. */
+		/* other flags exists, but normally, they never be matched. */
 		default:
 			break;
 		}
@@ -6477,7 +6477,7 @@ void manage_client_side_cookies(struct stream *s, struct channel *req)
 				 * - delete the complete cookie if we're in insert+indirect mode, so that
 				 *   the server never sees it ;
 				 * - remove the server id from the cookie value, and tag the cookie as an
-				 *   application cookie so that it does not get accidentely removed later,
+				 *   application cookie so that it does not get accidently removed later,
 				 *   if we're in cookie prefix mode
 				 */
 				if ((s->be->ck_opts & PR_CK_PFX) && (delim != val_end)) {
@@ -7662,7 +7662,7 @@ void http_reset_txn(struct stream *s)
 
 	/* We must trim any excess data from the response buffer, because we
 	 * may have blocked an invalid response from a server that we don't
-	 * want to accidentely forward once we disable the analysers, nor do
+	 * want to accidently forward once we disable the analysers, nor do
 	 * we want those data to come along with next response. A typical
 	 * example of such data would be from a buggy server responding to
 	 * a HEAD with some data, or sending more than the advertised
-- 
2.19.1

Reply via email to