Expose Default Certificate Constants

[ErikMcClure]

If you control the TLS connection chain, there's no need to add a test certificate to the machine keychain. Instead, if the library simply exposed the already existing constants, these could be turned into a Certificate using tokio_native_tls::native_tls::Certificate::from_pem, which could then be fed into tokio_native_tls::native_tls::TlsConnector::builder().add_root_certificate inside a test, which is more convenient.

[FalkWoldmann]

Hi! Thanks for this PR. Builder is a private module (mod builder; in server/mod.rs), so pub const on these two lines doesn't make them reachable outside the crate. httpmock::server::builder::DEFAULT_CA_CERTIFICATE still fails with E0603: module builder is private. Confirmed by building it.

Fix: add pub use builder::{DEFAULT_CA_PRIVATE_KEY, DEFAULT_CA_CERTIFICATE}; to server/mod.rs (or make builder itself pub mod).

[ErikMcClure]

I added the pub use to server/mod.rs

[FalkWoldmann]

Awesome, thanks! Could you please feature-gate the constants? e.g

// src/server/builder.rs
#[cfg(feature = "https")]
pub const DEFAULT_CA_PRIVATE_KEY: &str = include_str!("../../certs/ca.key");
#[cfg(feature = "https")]
pub const DEFAULT_CA_CERTIFICATE: &str = include_str!("../../certs/ca.pem");

and

// src/server/mod.rs
pub use builder::HttpMockServerBuilder;
#[cfg(feature = "https")]
pub use builder::{DEFAULT_CA_PRIVATE_KEY, DEFAULT_CA_CERTIFICATE};

[ErikMcClure]

I featured-gated the constants and fixed the format, but the tests seem to fail for reasons that seem unrelated to this PR.