- Table based routing?
- Ripping out yahttp stuff, providing some basic classes only. ATM we do use a few yahttp include files (but no .cc)
- Some classes (NetmaskGroup, ComboAddress) need a UniquePtr Wrapper to keep them opaque (iputils
- cannot be included without big headages in bridge.hh at the moment). We could seperate
+ cannot be included without big headaches in bridge.hh at the moment). We could seperate
NetmaskGroup, but I expect ComboAddress to not work as it is union.
- Avoid unsafe? Can it be done?
*/
let tls = crate::web::rustweb::IncomingTLS {
certificate: config.tls.certificate.clone(),
key: config.tls.key.clone(),
- // password: config.tls.password.clone(), not supported (yet), ruttls does not handle it
+ // password: config.tls.password.clone(), not supported (yet), rusttls does not handle it
};
if !tls.certificate.is_empty() {
tls_enabled = true;
}
// Clippy does not seem to understand what cxx does and complains about needless_lifetimes
- // The warning is silenced that warning above
+ // The warning is silenced above
struct Request<'a> {
body: Vec<u8>,
uri: String,