On Nov 2, 2013, at 10:22 PM, Alan M. Carroll a...@network-geographics.com
wrote:
Sorry, running too many bugs. The fix is in TS-1424, commit f63b27d52.
It got mixed in because it was entangled with propagating a related error
condition for TS-1424.
Aha. Then yes, 4.0.2 does not have
I will be out tomorrow but then I will look at this again when I am back
online. I am sure I have seen this before and fixed it, I just need to find the
right issue.
Friday, November 1, 2013, 11:07:53 AM, you wrote:
So, is it right to conclude that compiling 4.0.2 will probably not help me.
Sorry, running too many bugs. The fix is in TS-1424, commit f63b27d52.
It got mixed in because it was entangled with propagating a related error
condition for TS-1424.
On Oct 31, 2013, at 8:15 PM, Alan M. Carroll a...@network-geographics.com
wrote:
Sorry, this slipped by me.
I think this is a known problem - try the patch from TS-1422 and see if that
fixes it.
Hmmm, the commit for TS-1422 says:
commit 043815e7a7a67b79a2ca6fdc3f6d6751e5150411
Author:
So, is it right to conclude that compiling 4.0.2 will probably not help me.
Sjaak
From: Leif Hedstrom
Sent: Friday, November 1, 2013 16:29
To: us...@trafficserver.apache.org; dev@trafficserver.apache.org
On Oct 31, 2013, at 8:15 PM, Alan M. Carroll a...@network-geographics.com
So, is it right to conclude that compiling 4.0.2 will probably not help me.
Sjaak
From: Leif Hedstrom
Sent: Friday, November 1, 2013 16:29
To: us...@trafficserver.apache.org; dev@trafficserver.apache.org
On Oct 31, 2013, at 8:15 PM, Alan M. Carroll a...@network-geographics.com
On Oct 31, 2013, at 8:15 PM, Alan M. Carroll a...@network-geographics.com
wrote:
Sorry, this slipped by me.
I think this is a known problem - try the patch from TS-1422 and see if that
fixes it.
But as far as i can tell, he’s running v4.0.1, which ought to have TS-1422?
Unless we have a
