@Robert
I didn’t notice the health poll is for the cache, thanks for pointing this out.
If so, it should work.
On 4/4/18, 10:23 PM, "Robert Butts" wrote:
@nbaoping
> So I suggest the change to the current TM to be like:
> 1) Separate the current polling of cache servers into t
>were we supposed to get rid of md5?
Yeah, that's what the PMC said on RC2:
https://lists.apache.org/thread.html/b1baae5033f17d2bb3ca35c1ff1f95523b49e194950d277306992a8c@%3Cdev.trafficcontrol.apache.org%3E
On Mon, Apr 9, 2018 at 3:58 PM, David Neuman
wrote:
> +1
> I tested the following:
> - bu
+1
I tested the following:
- building with the pkg command
- signatures
- checksums (were we supposed to get rid of md5? I must have missed that)
- installed and started traffic_stats
On Wed, Apr 4, 2018 at 11:04 AM, Robert Butts wrote:
> Hello All,
>
> I've prepared a release for v2.2.0-RC4
>
Hey Zhilin,
Regarding the ports configuration. Even though I believe modeling will be
cleaner if the port and IP are set together, you are probably correct - it
is reasonable to consider the Port per IP flexibility as a future extension
and avoid it for now.
Still, I would suggest to at-least mod
Thanks for the example, Jeremy. Do we have any guidelines about
whether or not the `?(.json) ` suffix should be supported for new API
endpoints? It seems pointless because the API will always return JSON.
- Rawlin
On Fri, Apr 6, 2018 at 3:14 PM, Jeremy Mitchell wrote:
> Rawlin,
>
> I have submit
I am fine if we move in this direction, but I think we should be very
careful not to break existing functionality. We need to make sure that if
we do change from path params to query params that we update our API
versions, documentation, and tests accordingly.
Unless I am reading it wrong, it look
