From 938889961a6ed02bbb8fb393c7f71d3a340eecb4 Mon Sep 17 00:00:00 2001 From: Screeny Date: Tue, 16 May 2017 10:01:31 +0200 Subject: [PATCH] Fix typo in addheadermultiline.md --- docs/en/plugins/addheadermultiline.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/en/plugins/addheadermultiline.md b/docs/en/plugins/addheadermultiline.md index 23904cf..0b23937 100644 --- a/docs/en/plugins/addheadermultiline.md +++ b/docs/en/plugins/addheadermultiline.md @@ -1,7 +1,7 @@ # [add_header_multiline] Multiline response headers You should avoid using multiline response headers, because: - * they are depricated (see [RFC 7230](https://tools.ietf.org/html/rfc7230#section-3.2.4)); + * they are deprecated (see [RFC 7230](https://tools.ietf.org/html/rfc7230#section-3.2.4)); * some HTTP-clients and web browser never supported them (e.g. IE/Edge/Nginx). ## How can I find it? @@ -22,4 +22,4 @@ more_set_headers -t 'text/html text/plain' ``` ## What can I do? -The only solution is to never use multiline response headers. \ No newline at end of file +The only solution is to never use multiline response headers.