From d48ab9601b083cb3bdb765de903dd16c89615791 Mon Sep 17 00:00:00 2001 From: nabijaczleweli Date: Sun, 15 Oct 2017 15:00:49 +0200 Subject: [PATCH] docs(headers): fix >-quote formatting '>'s as non-first characters are just '>'s (rustfmt probably broke the line) --- src/header/common/content_length.rs | 2 +- src/header/common/pragma.rs | 1 - src/proto/response.rs | 2 +- 3 files changed, 2 insertions(+), 3 deletions(-) diff --git a/src/header/common/content_length.rs b/src/header/common/content_length.rs index 45fd6572d1..f5922dad29 100644 --- a/src/header/common/content_length.rs +++ b/src/header/common/content_length.rs @@ -19,7 +19,7 @@ use header::{Header, Raw, parsing}; /// [RFC7230](http://tools.ietf.org/html/rfc7230#section-3.3.2): /// /// > A sender MUST NOT send a Content-Length header field in any message -/// that > contains a Transfer-Encoding header field. +/// > that contains a Transfer-Encoding header field. /// /// # ABNF /// ```plain diff --git a/src/header/common/pragma.rs b/src/header/common/pragma.rs index 8b1c9801cd..fca49746f9 100644 --- a/src/header/common/pragma.rs +++ b/src/header/common/pragma.rs @@ -10,7 +10,6 @@ use header::{Header, Raw, parsing}; /// > that they will understand (as Cache-Control was not defined until /// > HTTP/1.1). When the Cache-Control header field is also present and /// > understood in a request, Pragma is ignored. - /// > In HTTP/1.0, Pragma was defined as an extensible field for /// > implementation-specified directives for recipients. This /// > specification deprecates such extensions to improve interoperability. diff --git a/src/proto/response.rs b/src/proto/response.rs index 950b963ee9..0154cb15f1 100644 --- a/src/proto/response.rs +++ b/src/proto/response.rs @@ -200,7 +200,7 @@ pub fn from_wire(incoming: ResponseHead, body: Option) -> Response { } } -/// Splits this response into a MessageHead and its body +/// Splits this response into a `MessageHead` and its body #[inline] pub fn split(res: Response) -> (MessageHead, Option) { let head = MessageHead:: {