Hi,
I was working on fixing header_rewrite set-redirect, but then I ran into an
issue in the server code where TSHttpTxnSetHttpRetStatus causes ATS to
close the connection before it returns anything the client. I tested the
@status functionality in regex_remap and the same issue happens.
This is
Hi All,
We're doing a sponsored dinner tonight at Wynkoop Brewery, at 18th and
Wynkoop, at 7pm. It would be great to see you all there.
Brian
Hi dev@trafficserver,
At dinner last night, I was mentioning to some folks the test suite
that we've been using over on Serf (http://code.google.com/p/serf/)
called MockHTTPinC.
Lieven has it up on GitHub at:
https://github.com/lgov/MockHTTPinC
You can see some examples of it used by Serf at:
ht
On Apr 10, 2014, at 5:54 AM, zw...@apache.org wrote:
> Repository: trafficserver
> Updated Branches:
> refs/heads/master 4b6c8e022 -> 77c5cf39b
>
>
> TS-2703 Add a text log format to escalate plugin
>
>
> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> Commit: http://git-
On Apr 10, 2014, at 5:54 AM, zw...@apache.org wrote:
> TS-2690 Make the escalate plugin support URL and Host redirects
>
> TS-2690 Support multiple status codes for each rule, e.g. 403,404:
>
>
> Project: http://git-wip-us.apache.org/repos/asf/trafficserver/repo
> Commit: http://git-wip-us.apac
Am Donnerstag, 10. April 2014, 17:08:41 schrieb Yunkai Zhang:
> On Thu, Apr 10, 2014 at 5:00 PM, Wolfgang Walter
wrote:
> > Am Donnerstag, 10. April 2014, 10:29:27 schrieb Yunkai Zhang:
> > > Why we need to log these information?
> >
> > We here need them to distinquish how the client used the pr
On Thu, Apr 10, 2014 at 5:00 PM, Wolfgang Walter wrote:
> Am Donnerstag, 10. April 2014, 10:29:27 schrieb Yunkai Zhang:
> > Why we need to log these information?
>
> We here need them to distinquish how the client used the proxy. We have
> different ips (and ports) for explicit and transparent use
Am Donnerstag, 10. April 2014, 10:29:27 schrieb Yunkai Zhang:
> Why we need to log these information?
We here need them to distinquish how the client used the proxy. We have
different ips (and ports) for explicit and transparent use.
>
> And there are client_host_{ip|port}, the name of client_s
