fix a few docs bugs and export HttpResponseContent

Author: iximeow

dropshot/src/error.rs

@@ -347,11 +347,11 @@ impl HttpError {
     /// If this error does not already have a header map (`self.header_map` is
     /// `None`), this method creates one.
     ///
-    /// Unlike [`HttpError::set_header`], this method takes `self` by value,
+    /// Unlike [`HttpError::add_header`], this method takes `self` by value,
     /// allowing it to be chained to form an expression that returns an
     /// `HttpError`. However, because this takes `self` by value, returning an
     /// error for an invalid header name or value will discard the `HttpError`.
-    /// To avoid this, use [`HttpError::set_header`] instead.
+    /// To avoid this, use [`HttpError::add_header`] instead.
     ///
     /// # Returns
     ///

dropshot/src/error_status_code.rs

@@ -16,7 +16,7 @@ use std::fmt;
 /// Alternatively, constants are provided for known error status codes, such as
 /// [`ErrorStatusCode::BAD_REQUEST`], [`ErrorStatusCode::NOT_FOUND`],
 /// [`ErrorStatusCode::INTERNAL_SERVER_ERROR`], and so on, including those in
-/// the IANA HTTP Status Code Registry](
+/// the [IANA HTTP Status Code Registry](
 /// https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml).
 /// Using these constants avoids the fallible conversion from an
 /// [`http::StatusCode`].
@@ -425,7 +425,7 @@ impl_status_code_wrapper! {
 ///
 /// Alternatively, constants are provided for known error status codes, such as
 /// [`ClientErrorStatusCode::BAD_REQUEST`],
-/// [`ClientErrorStatusCode::NOT_FOUND`], including those in the IANA HTTP
+/// [`ClientErrorStatusCode::NOT_FOUND`], including those in the [IANA HTTP
 /// Status Code Registry](
 /// https://www.iana.org/assignments/http-status-codes/http-status-codes.xhtml).
 /// Using these constants avoids the fallible conversion from an

dropshot/src/lib.rs

@@ -909,6 +909,7 @@ pub use handler::FreeformBody;
 pub use handler::HttpCodedResponse;
 pub use handler::HttpResponse;
 pub use handler::HttpResponseAccepted;
+pub use handler::HttpResponseContent;
 pub use handler::HttpResponseCreated;
 pub use handler::HttpResponseDeleted;
 pub use handler::HttpResponseError;

dropshot/src/test_util.rs

@@ -243,7 +243,7 @@ impl ClientTestContext {
     }
 
     /// Temporarily configures the client to expect `E`-typed error responses,
-    /// rather than [`dropshot::HttpError`] error responses.
+    /// rather than [`dropshot::HttpError`][`crate::HttpError`] error responses.
     ///
     /// `ClientTestContext` expects that all error responses are
     /// `dropshot::HttpError`. For testing APIs that return other error types, this