apimock-server 5.0.1

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
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94

//! Turn a matched `Respond` declaration into an HTTP response.
//!
//! # Why this is a server-side free function and not a `Respond` method
//!
//! Pre-5.0, `Respond::response(...)` lived on the type itself. That
//! method built a `hyper::Response<BoxBody>` and touched the server's
//! file-response / text-response / status-response helpers. To keep
//! `apimock-routing` free of hyper-body construction (so a future GUI
//! can depend on it cheaply), that work moved here.

use apimock_routing::{ParsedRequest, Respond};
use console::style;
use std::path::Path;

use crate::{
    http_util::delay_response,
    response::{
        error_response::internal_server_error_response,
        file_response::FileResponse,
        status_code_response::{status_code_response, status_code_response_with_message},
        text_response::text_response,
    },
    respond_util::full_file_path,
    types::BoxBody,
};

/// Produce the HTTP response for a matched `Respond` declaration.
///
/// # Why the branches are ordered file → text → status → error
///
/// The fields are mutually specialised:
/// - `file_path` serves a file (possibly with CSV→JSON conversion).
/// - `text` + `status` yields a custom-status text response.
/// - `text` alone yields a plain 200 text response.
/// - `status` alone yields an empty body with that status.
///
/// `Respond::validate` rejects nonsensical combinations at startup, so
/// hitting the final `Err` branch means something slipped past
/// validation — a real bug, not user input.
pub async fn respond_response(
    respond: &Respond,
    dir_prefix: &str,
    parsed_request: &ParsedRequest,
) -> Result<hyper::Response<BoxBody>, hyper::http::Error> {
    if let Some(delay_ms) = respond.delay_response_milliseconds {
        delay_response(delay_ms).await;
    }

    let request_headers = &parsed_request.component_parts.headers;

    // file_path → file/CSV/JSON response
    if let Some(file_path) = respond.file_path.as_ref() {
        let Some(full_file_path) = full_file_path(file_path.as_str(), dir_prefix) else {
            log::error!(
                "{}:\n{} (prefix = {})",
                style("file not found").red(),
                file_path,
                dir_prefix,
            );
            return internal_server_error_response(
                "failed to get response file",
                request_headers,
            );
        };

        // dir_prefix is used only for the file-not-found message above;
        // the actual read happens against the resolved full_file_path.
        let _ = Path::new(dir_prefix);

        return FileResponse::new_with_csv_records_jsonpath(
            full_file_path.as_str(),
            respond.headers.as_ref(),
            respond.csv_records_key.clone(),
            request_headers,
        )
        .file_content_response()
        .await;
    }

    if let Some(text) = respond.text.as_ref() {
        return match respond.status_code.as_ref() {
            Some(status_code) => {
                status_code_response_with_message(status_code, text.as_str(), request_headers)
            }
            None => text_response(text.as_str(), None, respond.headers.as_ref(), request_headers),
        };
    }

    if let Some(status_code) = respond.status_code.as_ref() {
        return status_code_response(status_code, request_headers);
    }

    internal_server_error_response("invalid respond def", request_headers)
}