You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@serf.apache.org by be...@qqmail.nl on 2015/10/30 09:32:53 UTC

RE: svn commit: r1711392 - in /serf/trunk: buckets/response_buckets.cserf_bucket_types.h

See yesterdays mail from the mod_speed project.

They want to user serf on an intermediate server to fetch the response from a server using serf and then send it out to clients after some filtering.

They currently maintain a local patch to support this usecase.

I agree that I don't see a good reason for final clients, but I think it is useful to support this usecase.

Bert

Sent from Mail for Windows 10



From: Greg Stein
Sent: vrijdag 30 oktober 2015 07:05
To: Bert Huijben
Cc: dev@serf.apache.org
Subject: Re: svn commit: r1711392 - in /serf/trunk: buckets/response_buckets.cserf_bucket_types.h


On Thu, Oct 29, 2015 at 7:23 PM, <rh...@apache.org> wrote:
>...

> +/**
> + * Ask the response @a bucket, to decode content based on the value of the
> + * 'Content- Encoding' header, or not. The default setting of a response
> + * bucket is to decode when the header is found.
> + */
> +void serf_bucket_response_decode_content(
> +    serf_bucket_t *bucket,
> +    int decode);
>

What's this for? Why would somebody turn *off* content decoding?

Cheers,
-g