Hi, This patch deals with typos in the example files. To be more specific the error 500 example page and the transparent_proxy.cfg page. For the later, it is all in the comments but still user-visible as those are examples.
I wasn't sure if you consider the examples files as documentation or user-visible code, so I used the MINOR severity for the patch. The patch is attached, but if you want to view the diff online, you can check: https://github.com/haproxy/haproxy/compare/master...aerostitch:minor_examples_typo Thanks for your help, Joseph
From 7bda552f46cd5d22f8536fa01259a3c18515b1d9 Mon Sep 17 00:00:00 2001 From: Joseph Herlant <aerosti...@debian.org> Date: Tue, 13 Nov 2018 20:01:24 -0800 Subject: [PATCH] MINOR: fix typos in the examples files To be more specific the error 500 example page and the transparent_proxy.cfg page. For the later, it is all in the comments but still user-visible as those are examples. --- examples/errorfiles/500.http | 2 +- examples/transparent_proxy.cfg | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-) diff --git a/examples/errorfiles/500.http b/examples/errorfiles/500.http index ebf7d47f..9c3be965 100644 --- a/examples/errorfiles/500.http +++ b/examples/errorfiles/500.http @@ -4,6 +4,6 @@ Connection: close Content-Type: text/html <html><body><h1>500 Internal Server Error</h1> -An internal server error occured. +An internal server error occurred. </body></html> diff --git a/examples/transparent_proxy.cfg b/examples/transparent_proxy.cfg index 0ecb20d4..b514ae3b 100644 --- a/examples/transparent_proxy.cfg +++ b/examples/transparent_proxy.cfg @@ -39,11 +39,11 @@ backend TransparentBack_http # /sbin/sysctl net.link.ether.ipfw=1 # ipfw add 10 fwd localhost tcp from 192.168.0.40 80 to any in recv em0 # -# the above does the folowing: +# the above does the following: # - load the ipfw kernal module # - set pf as the outer firewall to keep control of routing packets for example to route them to a non-default gateway # - enable ipfw -# - set a rule to catches reply traffic on em0 comming from the webserver +# - set a rule to catches reply traffic on em0 coming from the webserver # # --- Step 2 --- # To also make the client connection transparent its possible to redirect incomming requests to HAProxy with a pf rule: -- 2.19.1
