/// This is largely the same as "http" but the caller ID isn't checked
/// This allows other canisters to call this endpoint with arbitrary
/// data. This could lead to security issues if you're using
/// connection metadata to identify users.
/// If you're not sure what function to use, use "http"
This is largely the same as "http" but the caller ID isn't checked
This allows other canisters to call this endpoint with arbitrary
data. This could lead to security issues if you're using
connection metadata to identify users.
If you're not sure what function to use, use "http"
This is largely the same as " http " but the caller ID isn ' t checked This allows other canisters to call this endpoint with arbitrary data . This could lead to security issues if you ' re using connection metadata to identify users . If you ' re not sure what function to use use " http "
pub fn http_unchecked<F>(handler: F)
where
    F: FnOnce(RequestWrapper) -> Response,
{
    dfn_core::over(dfn_candid::candid_one, handler)
}
pub fn http_unchecked < F > ( handler : F ) where F : FnOnce ( RequestWrapper ) -> Response , { dfn_core :: over ( dfn_candid :: candid_one , handler ) }
This is largely the same as "http" but the caller ID isn't checked
This allows other canisters to call this endpoint with arbitrary
data.
This is largely the same as " http " but the caller ID isn ' t checked This allows other canisters to call this endpoint with arbitrary data .
handler
F