Those who had to deal with nginx plugins, I feel your pain...
[2] https://github.com/apache/trafficserver/tree/master/example/...
11–20 of 40 posts
Those who had to deal with nginx plugins, I feel your pain...
[2] https://github.com/apache/trafficserver/tree/master/example/...
Subject should be changed to "Apache Traffic Server Security Fixes" or similar. Looks like the "News" is that Nov 2 they released 8.1.3 and 9.1.1 with "security fixes". However, after digging for half an hour I can't tell what the nature of the security fix is. Changelogs and issues related to these releases don't highlight any particular security issues or what the impacts are.
I submitted the link before the new release with security fixes was announced, without that in mind. Moreover, the link points to the project page and not the release. I submitted because I found the project interesting but somewhat low-key, and I thought people like me would find it interesting.
Subject should be changed to "Apache Traffic Server Security Fixes" or similar. Looks like the "News" is that Nov 2 they released 8.1.3 and 9.1.1 with "security fixes". However, after digging for half an hour I can't tell what the nature of the security fix is. Changelogs and issues related to these releases don't highlight any particular security issues or what the impacts are.
> Subject should be changed to "Apache Traffic Server Security Fixes" or similar. I submitted the link before the new release with security fixes was announced, without that in mind. Moreover, the link points to the project page and not the release. I submitted because I found the project interesting but somewhat low-key, and I thought people like me would find it interesting.
Earlier quoted context omitted.
> Subject should be changed to "Apache Traffic Server Security Fixes" or similar. I submitted the link before the new release with security fixes was announced, without that in mind. Moreover, the link points to the project page and not the release. I submitted because I found the project interesting but somewhat low-key, and I thought people like me would find it interesting.
Fair enough, but I stand by that the news is that there's a security fix.
Specifically, I install it, point it at a large raw disk partition, and drop in my config files (largely consisting of routing rules for where to get the origin based on the request), and trafficserver just goes to town. It's a perfect use case for the ephemeral storage on virtual instances.
Looks recent, at first I thought it was webserver from the 90's...
Lots of choices in the this space... - this tool (apache traffic server) - regular apache can proxy/cache/route - nginx - traefik - haproxy - envoy - kong - ...more Then it also somewhat intersects with less directly related things in other spaces, like squid, varnish, istio, and so on. Is there some document somewhere that goes over the choices, overlaps, etc?
Looks recent, at first I thought it was webserver from the 90's...
Lots of choices in the this space... - this tool (apache traffic server) - regular apache can proxy/cache/route - nginx - traefik - haproxy - envoy - kong - ...more Then it also somewhat intersects with less directly related things in other spaces, like squid, varnish, istio, and so on. Is there some document somewhere that goes over the choices, overlaps, etc?
Which of those can proxy TCP, as opposed to HTTP? Haproxy can.