BodyHandle

An invalid body handle.

This is primarily useful to represent uninitialized values when using the interfaces in fastly_sys.

Append another body onto the end of this body.

This operation is performed in amortized constant time, and so should always be preferred to reading an entire body and then writing the same contents to another body.

The other body will no longer be valid after this call.

Get the underlying representation of the handle.

Safety

This should only be used when calling the raw ABI directly, and care should be taken not to reuse or alias handle values.

Get a mutable reference to the underlying u32 representation of the handle.

Safety

This should only be used when calling the raw ABI directly, and care should be taken not to reuse or alias handle values.

Close the BodyHandle by removing it from the host Session. This will close out streaming and non streaming bodies. Care must be taken to only close out the handle if the body is not being written to or read from anymore. If the handle has already been closed an error will be returned.

Examples

let mut body = BodyHandle::new();
body.write_all(b"You're already closed.")?;
// The handle is not being used in a request and doesn't refer to any
// response body so we can close this out
body.close()?;

Get a handle to the client request body.

This handle may only be retrieved once per execution, either through this function or through client_request_and_body().

Make a handle from its underlying representation.

Safety

This should only be used when calling the raw ABI directly, and care should be taken not to reuse or alias handle values.

Read the entirety of the body into a byte vector.

Memory usage

This method will cause the entire body to be buffered in WebAssembly memory. You should take care not to exceed the WebAssembly memory limits, and consider using Read methods to control how much of the body you process at once.

Read the entirety of the body into a String, interpreting the bytes as UTF-8.

Memory usage

This method will cause the entire body to be buffered in WebAssembly memory. You should take care not to exceed the WebAssembly memory limits, and consider using Read methods to control how much of the body you process at once.

Panics

If the body does not contain a valid UTF-8 string, this function will panic. To explicitly handle the possibility of invalid UTF-8 data, use into_bytes() and then convert the bytes explicitly with a function like String::from_utf8.

Turn a handle into its representation without closing the underlying resource.

Safety

This should only be used when calling the raw ABI directly, and care should be taken not to reuse or alias handle values.