On Feb 23, 2014, at 10:47 AM, Brian Geffon wrote:
> Doesn't the http connect parse headers anyway?
Yep
> Isn't the address only used for local host proxying?
local host proxying? I followed the code a little way and I thought that it is
the address the connection was accepted on? I used to th
Doesn't the http connect parse headers anyway? Isn't the address only used
for local host proxying?
Brian
On Sunday, February 23, 2014, Shu Kit Chan wrote:
> ESI plugin unfortunately still uses TSFetchUrl and therefore cannot handle
> ipv6 client addresses.
>
>
> On Sun, Feb 23, 2014 at 8:19 AM
ESI plugin unfortunately still uses TSFetchUrl and therefore cannot handle
ipv6 client addresses.
On Sun, Feb 23, 2014 at 8:19 AM, James Peach wrote:
> On Feb 20, 2014, at 2:43 PM, kic...@apache.org wrote:
>
> > Repository: trafficserver
> > Updated Branches:
> > refs/heads/master d3e4614bf ->
GitHub user jablko opened a pull request:
https://github.com/apache/trafficserver/pull/44
TS-2584 Fix failed assert transforming and caching negative responses
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/jablko/trafficserver
On Feb 20, 2014, at 2:43 PM, kic...@apache.org wrote:
> Repository: trafficserver
> Updated Branches:
> refs/heads/master d3e4614bf -> d94a47ba8
>
>
> TS-2579: remove ipv4 limit on FetchSM and TSFetchUrl/TSFetchPages
What's the use case for this fix? One thing I just noticed is that all my code
