Crate icap 

Available on crate feature icap only.

Internet Content Adaptation Protocol (ICAP) support for Rama.

The crate is layered so applications can use only the level they need:

• codec and proto provide allocation-free, no_std wire syntax;
• message owns encoded messages;
• client and server stream ICAP transactions through Rama I/O;
• http adds typed HTTP messages and the HTTP adaptation layer.

The default build contains the protocol and codec only. Enable std for client/server I/O, or http for typed HTTP adaptation (http implies std). Live connections use compatible parsing by default; strict parser policies remain available through io::ConnectionOptions.

See the complete HTTP(S) proxy and embedded ICAP server in Rama’s http_icap_proxy example.

Rama

Crate used by the end-user rama crate and rama crate authors alike.

Learn more about rama:

• GitHub: https://github.com/plabayo/rama
• Book: https://ramaproxy.org/book/

Modules

clientstd

Standalone streaming ICAP client transactions.

codec

Borrowed ICAP wire decoders and fixed-buffer encoders.

httphttp

Typed HTTP integration for ICAP messages and streaming bodies.

iostd

Bounded asynchronous ICAP framing over an arbitrary byte stream.

messagestd

Owned ICAP message metadata for asynchronous transactions.

proto

ICAP protocol values independent of transport I/O.

serverstd

Standalone streaming ICAP server transactions.