You can indicate the number of bytes that you are going to write to the
output vio in that call. INT64_MAX is specified when the content length is
not known up front, in which case ATS will either use a chunked transfer
encoding or close the connection when that is not feasible.
Otto
2012/11/12 O
IN the null transform plugin, there is a line of code that reads:
data->output_vio = TSVConnWrite(output_conn, contp, data->output_reader,
INT64_MAX);
It seems to happen prior to writing anything to the output_vio.
Does anyone know what is happening here? Specifically why is INT64_MAX being
+1
On Mon, 2012-11-12 at 14:27 +, iga...@apache.org wrote:
> Updated Branches:
> refs/heads/3.2.x 3f5c75ded -> 15dea758d
>
>
> voted. You should too.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> Commit: http://git-wip-us.apache.org/repos/asf/trafficserver/com
+1
- Original Message -
> Updated Branches:
> refs/heads/3.2.x 43326240b -> 3f5c75ded
>
>
> Added proposal for range acceleration fix.
>
> + Range acceleration fix: Disable range acceleration by changing
> + is_pread_capable to always return false. Put the current code in
> an
> +
