Re: Notification when objects are removed from the cache (disk storage)

There isn’t. However, you can see how often the disks are churned (via metrics), which at least gives you an estimate of how long objects are staying in the cache. If the disks wraps once a week, objects are likely to stay in the cache for a week. — Leif > On Apr 22, 2024, at 07:00, Pavel

Re: Using Apache Traffic Server as HTTP client to store some content in the storage

eated by a Yahoo-ligan. ;)On Fri, Apr 19, 2024 at 9:51 AM Leif Hedstrom <zw...@apache.org> wrote:We discussed this in the slack channel. Probably the best option for you (other than writing a new plugin) is to use the background_fetch plugin. You will still need to trigger a download, but

Re: Using Apache Traffic Server as HTTP client to store some content in the storage

We discussed this in the slack channel. Probably the best option for you (other than writing a new plugin) is to use the background_fetch plugin. You will still need to trigger a download, but you can avoid having to wait for the full response in the client. So, what you’d do is curl -H

Re: [VOTE] Release Apache Traffic Server 9.2.4 (RC0)

+1 > On Apr 3, 2024, at 9:54 AM, Bryan Call wrote: > > I've prepared a release for 9.2.4. The release notes are available at: > > https://github.com/apache/trafficserver/milestone/69?closed=1 > > or for a brief ChangeLog: > >

Re: trafficserver documentation

For the missing configs, yes you just add the ones you want manually. The sample config file only includes the most common settings, to avoid confusion. For your second question, look at the remap.config docs and examples. You are looking for a directive named “redirect”. Cheers, — Leif On

Re: [E] [PROPOSAL] Remove "proxy.process" prefix from all core metrics

:). — Leif > > Thanks. > Damian. > > On Mon, Dec 18, 2023 at 3:29 AM Leif Hedstrom wrote: > >> Through all our cleanup and refactoring in the past, as far as I can tell, >> all metrics are now prefixed with proxy.process. >> >> This seems a li

[PROPOSAL] Remove "proxy.process" prefix from all core metrics

Through all our cleanup and refactoring in the past, as far as I can tell, all metrics are now prefixed with proxy.process. This seems a little superfluous. I’d like to suggests one of two options: 1. Just drop the prefix entirely. 2. Replace the prefix with “ats”. Thoughts? — Leif

[Proposal] Remove tsxs from ATS v10.0.0

We’ve discussed of this tool in slack and meetup, and the consensus is that with the migration to CMake, using the cmake or package config tools eliminates the need for this old tool. So the suggestion is that we’ll remove it from ATS v10. Let us know if you have a problem with this by

[Proposal] Remove WCCP from ATS v10.0.0

Hi y’all, I’d like to propose that we remove all WCCP support and code from ATS v10.0.0. WCCP is a protocol that isn’t maintained and supported by Cisco, and hasn’t been for a long time. It’s lacking in important “modern” features such as IPv6. If anyone still has a use or need of WCCP, please

[PROPOSAL] Remove the old HTTP stats and cache inspection pages

I’d like to propose that we remove these pages from the ATS v10 release. Not only are they not maintained (and haven’t been for a long time, so some of it doesn’t work), they generally don’t have a whole lot of useful information. The notion of running this (sort of ) minimal HTTP server

[PROPOSAL] Remove the experimental/cache_key_genid plugin for v10.0.0

This plugin is experimental, not maintained, and I think not used (there are better ways to manage genIDs now). Removing it simplifies our build system, and maintenance of plugins. Let us know if you have a problem wit this — Leif

Re: How to proxy to ws on local unix socket

Yeh this is not possible at this time. It’s a feature we have been looking to add for quite a while, just hasn’t been a priority for anyone. — Leif > On Oct 24, 2023, at 03:50, Philipp wrote: > > Hi, > > I am using ATS (successfully) to forward incoming websocket connections to a > local

Re: [PROPOSAL] Remove persistent storage for HostDB

nce. Thanks! — Leif > > Using /etc/hosts is very useful for troubleshooting, so I can point to a > specific origin server temporarily and still have the proper SNI and host > header. > > On Tue, Sep 5, 2023 at 11:38 AM Leif Hedstrom wrote: > >> I’d like to remove the featur

Re: [PROPOSAL] Remove persistent storage for HostDB

ries are likely already expired anyways. The whole point of removing this in v10.0 is that it would allow us (with less effort) to replace HostDB with something better, without having to wait until v11.0. Cheers, — Leif >On Tuesday, September 5, 2023 at 08:38:03 AM PDT, Leif Hedstrom &g

Re: [PROPOSAL] Remove persistent storage for HostDB

> On Sep 5, 2023, at 9:44 AM, David Carlin wrote: > > These settings are for /etc/hosts - are their removal required to get rid > of persistent storage? > >proxy.config.hostdb.host_file.path >proxy.config.hostdb.host_file.interval Hmmm, that was not the intent, let me look at the

[PROPOSAL] Remove persistent storage for HostDB

I’d like to remove the feature for persistent HostDB storage for ATS v10.0. In ATS v9 we made this disabled by default, and removing this feature completely would make it easier in the future to improve and replace HostDB itself with better containers. And, persistent DNS caching is better done

[DISCUSS] Can we replace / eliminate some "avg" and "per_sec" metrics?

While going through ATS to rewrite the metrics (still being evaluated if viable), I’ve come to realize that we have a number of metrics that are not particularly useful. What’s worse, there’s some serious implications for these particular metrics making the calculation of them expensive and

[Discuss, Proposal] Plugins promotions, deprecations and removals for ATS v10.0.0

Hi all, as part of our major release cleanup, I’d like to make the following proposals to the current set of plugins. Please let us know if you have problems with any of these changes, if not, lazy consensus applies. Remove these plugins: - * parent_select - This is

Re: Proposed new TS API function: TSYAMLCompatibilityCheck()

Hmmm, I’m not sure about this. Two reasons 1. We have compatibility checks already for plugins, and whatever yaml versions we have wi5 in a major version ought to always be compatible. If a plug-in uses TSYAML APIs, its compatibility ought to be guaranteed with the major version of ATS. This

Re: RAM cache on NVMe

quite common, considering SSD > and HDD differences. SSD-s are still too small to have proper CDN node > cache capacity and HDD-s are too slow in seeking for small files. > > Veiko > > > Kontakt Leif Hedstrom () kirjutas kuupäeval E, 10. > aprill 2023 kell 19:23: >

Re: RAM cache on NVMe

I don’t think you can have such control, at least not now. I think the best you could do is to shard your content (small vs large) into two (or more) domains, and then you can assign volumes based on those names. — Leif From hosting.config: # Primary destination specifiers are #

Re: Derivative Metrics removal.

> On Feb 14, 2023, at 9:47 AM, Damian Meden wrote: > > Hello guys. > In case you haven't noticed, our master branch no longer has the > `traffic_manager` binary. > There are still some references(docs, etc) and some other stuff that will > be erased as well, but one of the things that seems

[ANNOUNCE] Apache Traffic Server v9.2.0 is Released!

Apache Traffic Server v9.2.0 Released The Apache Software Foundation and the Apache Traffic Server (ATS) project are pleased to announce the release of Apache Traffic Server v9.2.0! ATS is a high performance, scalable HTTP Intermediary and proxy cache. It is used by several large internet

Re: [VOTE] Release Apache Traffic Server 9.2.0 (RC0)

cserver > > Building on rawhide required a (very minor) patch to support glibc 2.37 > changes (PR#9325), as did re-enabling the ppc64le arch (#9326). Awesome, thank you. We will include this with v9.2.1. Cheers, — Leif > > --Jered > > - On Jan 19, 2023, at 9:25 PM, Lei

Re: [VOTE] Release Apache Traffic Server 9.2.0 (RC0)

> On Jan 12, 2023, at 12:01 PM, Leif Hedstrom wrote: > > I've prepared a release for 9.2.0 (RC0), which is a minor release for 9.x, > and is still backwards compatible with all previous 9.x releases. This adds > quite a few new features, performance improvements and many

Re: [VOTE] Release Apache Traffic Server 9.2.0 (RC0)

+1 from me as well, of course. — Leif > On Jan 12, 2023, at 12:01 PM, Leif Hedstrom wrote: > > I've prepared a release for 9.2.0 (RC0), which is a minor release for 9.x, > and is still backwards compatible with all previous 9.x releases. This adds > quite a few new featur

[VOTE] Release Apache Traffic Server 9.2.0 (RC0)

I've prepared a release for 9.2.0 (RC0), which is a minor release for 9.x, and is still backwards compatible with all previous 9.x releases. This adds quite a few new features, performance improvements and many bug fixes. All in all, there are 588 PRs in this release, and is the result of well

Re: [VOTE] Release Apache Traffic Server 8.1.6 (RC0)

+1On Dec 15, 2022, at 12:41, Bryan Call wrote:I am calling the vote with 4 +1 votes.  We will publish the final release today.-BryanOn Dec 15, 2022, at 9:48 AM, Randall Meyer wrote: +1 - tested on macOS 13, builds, checks    On Thursday, December 15, 2022 at

Re: records.config to records.yaml

> On Sep 22, 2022, at 9:49 AM, Sudheer Vinukonda via users > wrote: > > My vote is for #2 (ie support a single format), but, if possible, it'd be > great if we can automatically convert the existing config files into YAML as > part of the upgrade. At the very least, we should provide a tool

Re: Initiating a "config reload" remotely

I guess a plugin would work, but I’d recommend doing something out of band instead. Integrate with existing management tools, or set up a new GRPC server or something. Having something user facing also be a control plane is a security incident waiting to happen. :) Cheers, — Leif > On Apr

[ANNOUNCE] Apache Traffic Server v9.1.2 is Released!

Apache Traffic Server v9.1.2 Released The Apache Software Foundation and the Apache Traffic Server (ATS) project are pleased to announce the release of Apache Traffic Server v9.1.2! ATS is a high performance, scalable HTTP Intermediary and proxy cache. It is used by several large internet

Re: [VOTE] Release Apache Traffic Server 9.1.2 (RC1)

Calling this vote, with 3 +1 votes(one from me as well obviously). Will upload the artifacts momentarily, and then send the announcement. — leif > On Feb 28, 2022, at 17:47, Leif Hedstrom wrote: > > I've prepared a release for 9.1.2 (RC1), which is a bug fix release

[VOTE] Release Apache Traffic Server 9.1.2 (RC1)

I've prepared a release for 9.1.2 (RC1), which is a bug fix release for 9.1.x and is backwards compatible. This adds a few fixes that was proposed after the first RC0 candidate. For a list of all PRs in this release, see https://github.com/apache/trafficserver/milestone/55?closed=1 or

Re: Building Traffic Server - static linking

changes to the core at a minimum. You would essentially have to tell it which plugins to build into the traffic_server binary, and bypass all the dlopen() dynamic loading of modules. Definitely tricky :). — Leif > > Thanks > > Nick > > From: Leif Hedstrom > Date:

Re: Building Traffic Server - static linking

> On Jan 4, 2022, at 12:41 PM, Nick Dunkin wrote: > > Hi > > We are wanting to deploy Traffic Server in a Docker container, and would like > to achieve the smallest possible container size. > > Is it possible to build Traffic Server with static linking, so that we can > run a single

Re: "F2F" (well, online) working group for a release schedule proposal

Ping on this, there has to be more than three people who cares about the next ~year releases? — Leif > On Nov 17, 2021, at 1:11 PM, Leif Hedstrom wrote: > > Hi all, > > As discussed in todays Summit, to come up with a release plan that works for > most of us, I’d l

"F2F" (well, online) working group for a release schedule proposal

Hi all, As discussed in todays Summit, to come up with a release plan that works for most of us, I’d like to have a “F2F" (online) with representatives from any organization / team that is interested in the upcoming releases. The goal would be to have an inclusive, but not too large, working

Re: [VOTE] Release Apache Traffic Server 9.1.1 (RC2)

+1 — leif > On Nov 1, 2021, at 3:49 PM, Bryan Call wrote: > > I've prepared a release for 9.1.1. The release notes are available at: > > > https://github.com/apache/trafficserver/pulls?q=is%3Aclosed+is%3Apr+milestone%3A9.1.1 > >

Re: [VOTE] Release Apache Traffic Server 8.1.3 (RC0)

> On Nov 1, 2021, at 9:42 AM, Bryan Call wrote: > > + 1 from me +1 — leif > > -Bryan > > >> On Oct 28, 2021, at 11:45 AM, Bryan Call > > wrote: >> >> I've prepared a release for 8.1.3. The release notes are available at: >> >> >>

Re: [VOTE] Release Apache Traffic Server 9.1.1 (RC1)

> On Nov 1, 2021, at 9:41 AM, Bryan Call wrote: > > +1 from me +1. — leif > > -Bryan > > >> On Oct 29, 2021, at 10:10 AM, Bryan Call > > wrote: >> >> I've prepared a release for 9.1.1. The release notes are available at: >> >> >>

Re: [VOTE] Release Apache Traffic Server 9.1.0 (RC0)

6:35 PM Randall Meyer > wrote: > +1 > > Built on macOS, tests passed. On Tuesday, August 10, 2021, 12:11:52 PM > PDT, Leif Hedstrom mailto:zw...@apache.org>> wrote: > > I've prepared a release for 9.1.0 (RC0), which is both a new feature and bug > fix rele

Re: [VOTE] Release Apache Traffic Server 9.1.0 (RC0)

And +1 from me obviously. — Leif > On Aug 13, 2021, at 15:29, Bryan Call wrote: > > +1 - Tested on Fedora 34 and passed all test. We are running 9.1.0 in > production with a few local patches to test upcoming features. > > -Bryan > > >> On Aug 10, 2021, at

Re: [VOTE] Release Apache Traffic server 8.1.2 (RC0)

+1 — Leif > On Jun 23, 2021, at 12:22 PM, Evan Zelkowitz wrote: > > Ive prepared a release for 8.1.2 (RC0), which is a bug fix release. For a > list of all PRs, see > >https://github.com/apache/trafficserver/milestone/47?closed=1 >

Re: [VOTE] Release Apache Traffic Server 9.0.2 (RC0)

+1 obviously, we’re running with many of these fixes in our test deployments. — Leif > On Jun 22, 2021, at 9:35 AM, Leif Hedstrom wrote: > > I've prepared a release for 9.0.2 (RC0), which is a bug fix release. For a > list of all PRs, see > > https://github.com/ap

[VOTE] Release Apache Traffic Server 9.0.2 (RC0)

I've prepared a release for 9.0.2 (RC0), which is a bug fix release. For a list of all PRs, see https://github.com/apache/trafficserver/milestone/48?closed=1 or for a brief ChangeLog (also attached below): https://github.com/apache/trafficserver/blob/9.0.x/CHANGELOG-9.0.2

Re: Illumos distros?

> On May 26, 2021, at 4:38 AM, Randy DuCharame wrote: > > Greetings, > > I was just curious if anyone's been building ATS 10 on any of the Illumos > distributions? (playing with OpenIndiana, OmniOS here) I've been a long time > fan of Solaris and used OpenSolaris exclusively for everything

[ANNOUNCE] Apache Traffic Server v9.0.1 is Released!

Apache Traffic Server v9.0.1 Released The Apache Software Foundation and the Apache Traffic Server (ATS) project are pleased to announce the release of Apache Traffic Server v9.0.1! ATS is a high performance, scalable HTTP Intermediary and proxy cache. It is used by several large internet

Re: [VOTE] Release Apache Traffic Server 9.0.1 (RC1)

Calling this vote with 5 +1’s and no -1’s. I’ll move the artifacts to the download site now, and will send out the announcement tomorrow. Thanks everyone for voting. — Leif > On Apr 10, 2021, at 4:21 PM, Leif Hedstrom wrote: > > I've prepared a another release for 9.0.1 (RC

Re: [VOTE] Release Apache Traffic Server 9.0.1 (RC1)

Calling this vote with 5 +1’s and no -1’s. I’ll move the artifacts to the download site now, and will send out the announcement tomorrow.Thanks everyone for voting.— LeifOn Apr 10, 2021, at 4:21 PM, Leif Hedstrom wrote:I've prepared a another release for 9.0.1 (RC1), which is a bug fix release

Re: [VOTE] Release Apache Traffic Server 9.0.1 (RC1)

+1 — Leif > On Apr 10, 2021, at 16:22, Leif Hedstrom wrote: > > I've prepared a another release for 9.0.1 (RC1), which is a bug fix release > only. For a list of all PRs, see > >https://github.com/apache/trafficserver/milestone/31?closed=1 > > > or

[VOTE] Release Apache Traffic Server 9.0.1 (RC1)

I've prepared a another release for 9.0.1 (RC1), which is a bug fix release only. For a list of all PRs, see https://github.com/apache/trafficserver/milestone/31?closed=1 or for a brief ChangeLog (also attached below):

Re: Apache Traffic Server on FreeBSD 13

816227928171d1f07de747f6a9a254b/src/tscore/EventNotify.cc#L34> > On Tue, Mar 30, 2021 at 9:29 AM Leif Hedstrom <mailto:zw...@apache.org>> wrote: > > >> On Mar 30, 2021, at 9:00 AM, Johan Hendriks > <mailto:joh.hendr...@gmail.com>> wrote: >> >> He

Re: Apache Traffic Server on FreeBSD 13

> On Mar 30, 2021, at 9:00 AM, Johan Hendriks wrote: > > Hello all, we use traffic server on FreeBSD 12.2 now and we like to switch to > FreeBSD 13 when it comes out. > So we did instaal the latest 13.0RC4 version but we can not build the port. > It erros out with an sys/epoll.h file not

Re: [VOTE] Release Apache Traffic Server 9.0.1 (RC0)

> On Mar 1, 2021, at 4:29 PM, Leif Hedstrom wrote: > > I've prepared a release for 9.0.1 (RC0), which is a bug fix release only. For > a list of all PRs, see > > https://github.com/apache/trafficserver/milestone/31?closed=1 > > > or for a brief Cha

[VOTE] Release Apache Traffic Server 9.0.1 (RC0)

I've prepared a release for 9.0.1 (RC0), which is a bug fix release only. For a list of all PRs, see https://github.com/apache/trafficserver/milestone/31?closed=1 or for a brief ChangeLog (also attached below): https://github.com/apache/trafficserver/blob/9.0.x/CHANGELOG-9.0.1

Re: [E] Basic caching setup?

Like I said, the default HTTPD would not send cache-control headers. — leif > On Feb 17, 2021, at 8:16 AM, Alan Carroll > wrote: > > Hmmm. I would enable debug tags and add the "cache" tag. That should give you > information on why the cache isn't caching. You can also chat with us at >

Re: Basic caching setup?

> On Feb 16, 2021, at 5:37 PM, Milos Dodic <2bearql...@gmail.com> wrote: > > Basic caching setup? > > > I am trying to have the most basic caching setup for a forward caching proxy. > Initially I tried changing the following options only: > > CONFIG proxy.config.http.cache.http INT 1 >

[ANNOUNCE] Apache Traffic Server v9.0.0 is Released!

Apache Traffic Server v9.0.0 Released The Apache Software Foundation and the Apache Traffic Server (ATS) project are pleased to announce the release of Apache Traffic Server v9.0.0! ATS is a high performance, scalable HTTP Intermediary and proxy cache. It is used by several large internet

Re: Question about parent.config

> On Jan 11, 2021, at 11:22 AM, Nick Dunkin > wrote: > > Hi all, > > I wish to use parent.config to control parent selection based on path > elements in the client URL. I know this is possible with the url_regex > primary qualifier, however my question is as

Re: [UPDATED: RC1] Re: [E] [VOTE] Release Apache Traffic Server 9.0.0 (RC0)

Calling this with 4 +1 votes and no -1’s. Thanks everyone for all the hard work on getting 9.0.0 ready! — Leif > On Dec 8, 2020, at 11:30, Leif Hedstrom wrote: > > We’ll cancel the 9.0.0-RC0 candidate, and I’ve prepared a new 9.0.0-RC1 > candidate, now available for

Re: [UPDATED: RC1] [E] [VOTE] Release Apache Traffic Server 9.0.0 (RC0)

+1 > On Dec 9, 2020, at 12:51, Bryan Call wrote: > > +1 - Tested on Fedora 33. We are running something very close to this RC in > production. > > -Bryan > > >> On Dec 8, 2020, at 10:29 AM, Leif Hedstrom wrote: >> >> We’ll cancel the 9.0.0-RC

[UPDATED: RC1] Re: [E] [VOTE] Release Apache Traffic Server 9.0.0 (RC0)

ttps://docs.trafficserver.apache.org/en/9.0.x/release-notes/whats-new.en.html > On Dec 2, 2020, at 1:39 PM, Susan Hinrichs wrote: > > The analysis of this crash is in > https://github.com/apache/trafficserver/issues/7338. > > On Wed, Dec 2, 2020 at 12:44 PM Leif Hedstrom wrote: > > >

Re: [E] [VOTE] Release Apache Traffic Server 9.0.0 (RC0)

> On Dec 2, 2020, at 10:01 AM, Susan Hinrichs wrote: > > -1 > > Concern about the second PR that Masaori identified. The original PR caused > asserts with a debug build.. I am testing another fix to this in production. > Looking good so far. I will update the PR shortly. > > Without

Re: [VOTE] Release Apache Traffic Server 8.1.1 (RC0)

+1 with the caveats of two known issues as documented in the release notes. — Leif > On Dec 1, 2020, at 14:21, Bryan Call wrote: > > I've prepared a release for 8.1.1. The release notes for 8.1.1 are > available at: > > >

Re: [ANNOUNCE] Apache Traffic Server Fall 2020 Summit

Since we are using Zoom, I believe we will be recording all sessions. — Leif > On Oct 24, 2020, at 18:24, Jason Yang wrote: > > Hi Bryan, > Will the talks be recorded and made available after summit? > > > Best, > Jason > > >> On Oct 24, 2020, at 1:26 PM, Bryan Call wrote: >>

Re: [VOTE] Release Apache Traffic Server 8.1.0 (RC0)

> On Aug 24, 2020, at 4:39 PM, Leif Hedstrom wrote: > > I've prepared a release for 8.1.0 (RC0), which is a release focusing on > stability and usability. In particular, we’ve made a number of improvements > to stability, reliability and performance for HTTP/2 in this release

Re: [VOTE] Release Apache Traffic Server 8.1.0 (RC0)

> On Aug 24, 2020, at 4:39 PM, Leif Hedstrom wrote: > > I've prepared a release for 8.1.0 (RC0), which is a release focusing on > stability and usability. In particular, we’ve made a number of improvements > to stability, reliability and performance for HTTP/2 in this release

[VOTE] Release Apache Traffic Server 8.1.0 (RC0)

I've prepared a release for 8.1.0 (RC0), which is a release focusing on stability and usability. In particular, we’ve made a number of improvements to stability, reliability and performance for HTTP/2 in this release. For a list of all PRs, see

Re: ATS Sizing

> On Aug 5, 2020, at 6:21 AM, Trilok Nathreddy wrote: > > Leif, > > We have around 30 k concurrent connections and most of the traffic is > telemetry traffic to upload diagnostic data ( <2KB) > > any considerations/best practices you can suggest? 30k active connections? How many QPS? How

Re: ATS Sizing

> On Jul 22, 2020, at 11:24 PM, Trilok Nathreddy wrote: > > Need a suggestion on how we can size the specs to deploy apache traffic > server on RHEL platforms ( cpu , ram needed) and also how to factor no of > concurrent connection, do we have any best practices to share too. This is

Re: Converting "records.config" to YAML

as your example). Lets not write box in the configuration values though :). This would be the time to do that as well, break records.config once, and be done with it. — Leif > > > On Wed, May 20, 2020 at 3:52 PM Leif Hedstrom <mailto:zw...@apache.org>> wrote: > >

Re: Converting "records.config" to YAML

notation to indicate descent along the objects. A simple rule would be to > forbid a name to contain "." and then use "." as a separator that indicates > to descend. Then the names would again be exactly as they are now and no > changes would be needed. This isn't really any di

Re: Converting "records.config" to YAML

IF we are going down this path, we should restructure the configuration name space now too. A lot of things makes no sense any more, including the proxy. prefix. I do agree with Randal though, we should use proper YAML structure for the name spaces, for both configurations and metrics. —

Re: cache read and write failures

Also, all this was discussed on the issue that was opened :). Which I think we should close, these metrics works exactly as expected albeit somewhat confusing. — Leif > On May 13, 2020, at 17:51, Alan Carroll > wrote: > >  > Cache misses count as read failures, so you should expect a lot

Re: Remap plugin DSO reloading - enabling and disabling

if so, like most features in ATS, don’t see *why* it should not be >> configurable (unless, making it so largely complicates things and is not >> worth the ROI). I think as long as there are ATS users that do not want to >> enable this behavior in prod, (at least not right away)

Re: Remap plugin DSO reloading - enabling and disabling

> On May 8, 2020, at 2:29 PM, Alan Carroll > wrote: > > > > On Fri, May 8, 2020 at 3:17 PM Leif Hedstrom <mailto:zw...@apache.org>> wrote: > > It should get reloaded for the second, not for the first. As far as I > understand, this is fine, the Ga

Re: Remap plugin DSO reloading - enabling and disabling

> On May 8, 2020, at 2:17 PM, Leif Hedstrom wrote: > > > >> On May 8, 2020, at 12:29 PM, Alan Carroll > <mailto:solidwallofc...@verizonmedia.com>> wrote: >> >> Consider a situation with option (1) with two remap rules: >> >> map http:

Re: Remap plugin DSO reloading - enabling and disabling

>> configuration to disable it if needed. Speaking specifically for TxnBox, I >> must forbid you from enabling DSO reloading. Even in your case, it might be >> reasonable to have this for plugins that you have not yet updated (which is >> actually the case with

Re: Remap plugin DSO reloading - enabling and disabling

> On May 7, 2020, at 8:12 PM, Alan Carroll > wrote: > > Leif; > > If the plugin can be global or remap but not both, I don't see why (2) limits > anything. The entire issue is irrelevant for such plugins, because the > situation of reloading the remap DSO but not the global cannot occur,

Re: Remap plugin DSO reloading - enabling and disabling

> On May 7, 2020, at 18:24, Alan Carroll > wrote: > >  > As part of the ATS 9 upgrade, a feature was added so that remap plugins could > have their DSO reloaded. This means not just the configuration, but the > implementation itself. While very useful, this has some unfortunate side >

Re: Remap causing parent servers to not have a match

ster”, and magic happens. — Leif > > On Thu, May 7, 2020 at 12:53 PM Josh Gitlin wrote: >> >> Thanks Leif! I am on 8.0.7, so maybe I should switch to 9 >> >> Josh Gitlin >> Principal DevOps Engineer >> jgit...@pinnacle21.com >> >> PINNACLE

Re: Remap causing parent servers to not have a match

> On May 7, 2020, at 1:05 PM, Josh Gitlin wrote: > > The more I dig into this, the more I realize I have gone horribly wrong > somewhere, as I seem to have just created an infinite parent proxy loop. So I > may need to RTFM again to fix this broken design! :) In ATS 9.x, there is a “self”

Re: New TS API TSSyncStatFindName()

> On Apr 14, 2020, at 1:23 PM, Sudheer Vinukonda > wrote: > > The existing TS API `TSStaFindName()` returns success if it's able to find > the stat in the stats hash table. This automatically becomes true for > persistent stats that get loaded from the stats snapshot, even when a >

Re: [VOTE] Release Apache Traffic Server 7.1.10 (RC0)

> On Apr 10, 2020, at 3:30 PM, Bryan Call wrote: > > I've prepared a release for 7.1.10. The release notes for 7.1.10 are > available at: > > > https://github.com/apache/trafficserver/pulls?utf8=✓=is%3Aclosed+is%3Apr+milestone%3A7.1.10 > > or for a brief ChangeLog: > >

Is anyone using the %{<...>records} log tag?

Accidentally (I blame Bryan …) we discovered that using this log tag can put some noticeable pressure on mutexes in the librecords subsystem. You’d use it like %<{proxy.process.version.server.build_number}record> Seeing that this (ab)use of librecord is not how it was intended for, if

Re: Coverity on ATS

> On Mar 6, 2020, at 2:44 AM, supraja sridhar > wrote: > > Hello, > > Are all ATS versions released only after the coverity issues have been > resolved? We can’t use Coverity any more, because they don’t support C++17. — Leif

Re: Changing the server url in a remap plugin before proxying

TSHttpTxnStatusSet(txnp, TS_HTTP_STATUS_INTERNAL_SERVER_ERROR); TSError("[%s] can't parse substituted URL string", PLUGIN_NAME); } Or any other appropriate APIs to modify the rri->requestUrl. Cheers, — Leif > > On Thu, Feb 27, 2020 at 9:25 AM Leif Hed

Re: [VOTE] Release Apache Traffic Server 7.1.9 (RC2)

> On Feb 26, 2020, at 2:54 PM, Bryan Call wrote: > > I've prepared a release candidate (rc2) for 7.1.9. The release notes for > 7.1.9 are available at: +1. — Leif

Re: Changing the server url in a remap plugin before proxying

> On Feb 27, 2020, at 10:18 AM, David Calavera wrote: > > Hi all, > > What's the best practice to change the origin server URL in remap plugins? > > We're working on a dynamic plugin that can proxy certain requests to a third > party service and we're not sure what's the best solution. >

Re: [VOTE] Release Apache Traffic Server 8.0.6 (RC1)

> On Feb 24, 2020, at 9:48 AM, Bryan Call wrote: > > +1 - Built and ran regression tests on Fedora 31. Unfortunately I can’t run > this version in production due to other dependencies. +1, tested in prod for 3 days, no crashes or noticeable issues. — leif

Re: Proposal for 9.x -- change X-Debug plugin's X-Cache order

> On Jan 16, 2020, at 3:41 PM, Miles Libbey wrote: > > Hi folks- > > In https://github.com/apache/trafficserver/pull/6328 we document the > X-Debug plugin's behavior with multiple proxies. Unfortunately, it's > done in the opposite order of the Via header (which is append, based > on

Re: [POLL] Dates for the ATS Spring Summit in London

> On Jan 24, 2020, at 10:00 AM, Bryan Call wrote: > > We are planning on having the ATS Spring Summit in London this year. Please > vote on the dates that you will be available if you plan on attending. > > The two options are the week of 5/4 or the week of 6/15. Please mark what > days

Re: path based hosting.config

> On Jan 12, 2020, at 12:16 PM, Jeremy Payne wrote: > > pulled the below lua from my work notes.. > > ++ > function send_request() >ts.server_request.header['Host'] = "real-origin.fqdn.com" > end > > function do_remap() > > -- this is what i use to segment various file types to

Re: path based hosting.config

> On Jan 12, 2020, at 10:47, Jeremy Payne wrote: > >  > Probably the easiest solution is to create another origin fqdn for your live > or vod content. > Then have the corresponding remap use that new fqdn as your origin fqdn > If you cant do that then there are some tricks you can play with

Re: ATS URL redirect

This doesn’t work unfortunately. If all you are changing is the host, just do that. If not, possibly you can do this with the regex_remap plug-in (not sure though). — Leif > On Dec 21, 2019, at 16:44, Satheeshkumar Rajagopal > wrote: > > STB.m3u8

Re: Building ATS 8.0.5 with clang-5.0 - compilation error

>>>>> TARGET_ARCH = x86_64 >>>>> TARGET_CPU = classic >>>>> >>>>> Compiler versions: >>>>> CC: clang version 5.0.2-svn328729-1~exp1~20180509124008.99 >>>>> (branches/release_50) /us

Re: Building ATS 8.0.5 with clang-5.0 - compilation error

Are you using the right STL, from LLVM, that had full C++17 support? — Leif > On Dec 18, 2019, at 21:40, supraja sridhar wrote: > >  > Hello, > > When building ATS 8.0.5 with clang-5.0 I get the following error - >> 12 make[3]: Entering directory >>

Re: TS_SSL_VERIFY_SERVER_HOOK

> On Nov 18, 2019, at 22:18, Susan Hinrichs wrote: > >  > That feature was added as TS_SSL_SERVER_VERIFY in 8.0.x. The name was > normalized to TS_SSL_VERIFY_SERVER_HOOK (to match the naming of > TS_SSL_VERIFY_CLIENT_HOOK) in the branch for 9.0.x. > > In theory, that functionality could

[REMINDER] "The ASF" Slack access

Hi all, just a reminder that we moved from IRC to “The ASF” Slack a while ago. If you are an Apache committer, you can join using your Apache email, for everyone else, just ask for an invite. The channel is #traffic-server. Cheers, — leif

Removing proxy.config. settings for filenames

Hi all, I’d like to remove all (most?) of the settings that lets you override configuration file names via records.config. We have other means to accomplish this (environment variables / runroot), and, many times, this “feature” has caused problems during upgrades. In addition, debug / warning

  1   2   3   4   5   6   7   8   9   10   >