apimock-server 5.19.0

HTTP(S) server runtime for apimock: listener loop, request handling, response building.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26

use hyper::HeaderMap;

use std::collections::HashMap;

use crate::{response_handler::ResponseHandler, types::BoxBody};

/// plain text response
///
/// `custom_headers` is applied *after* `with_text`, so an explicit
/// `content-type` in `custom_headers` wins over both `with_text`'s
/// `text/plain` default and `content_type` (itself only an inferred
/// default - e.g. a file-extension guess). This was previously reversed:
/// `with_text` ran last and unconditionally overwrote any explicit
/// `content-type` a caller had set (RFC 045 Defect 1b).
pub fn text_response(
    content: &str,
    content_type: Option<&str>,
    custom_headers: Option<&HashMap<String, Option<String>>>,
    request_headers: &HeaderMap,
) -> Result<hyper::Response<BoxBody>, hyper::http::Error> {
    let mut response_handler = ResponseHandler::default().with_text(content, content_type);
    if let Some(custom_headers) = custom_headers {
        response_handler = response_handler.with_headers(custom_headers.to_owned());
    }
    response_handler.into_response(request_headers)
}