Chunked Payload and vbComplete

The adapter can tell that no new HTTP message body bytes will be available (i.e. no more noteVbContentAvailable() calls) when the host application calls adapter::Xaction::noteVbContentDone(). This applies to all requests methods and all response status codes. This applies to all message transfer encodings, including chunked.

Please note that whether the entire virgin message body has been made available to the adapter by the host application depends on the noteVbContentDone() parameter value -- that atEnd parameter should be false if the body was truncated (e.g., the client did not sent the last-chunk before closing the connection to the proxy).

What causes the host application to call adapter::Xaction::noteVbContentDone()?
 In my adapter I hold the data for sometime as I am scanning the content the way it's done by clam av adapter. This works fine for most but does not for Google Voice to Text translation.
In the request I noticed that the ecap adapter keeps receiving data and adapter::Xaction::noteVbContentDone() is never called causing the request to eventually timeout.

> What causes the host application to call adapter::Xaction::noteVbContentDone()?

The end of virgin message body, as detected by the host application code, using HTTP protocol rules and such. When dealing with a chunked request, the body ends when the client sends last-chunk (i.e. the special zero-length chunk). The host application should know that and should call noteVbContentDone() after receiving and parsing last-chunk.

Please note that the client may not send last-chunk until seeing some or all of the origin server response. I do not know whether your particular client does that, but, AFAIK, there is nothing in HTTP protocol that prevents this kind of delay/wait, especially between a custom client and a custom origin server that expect that they are talking directly to each other.