I intended to use ATS in reverse proxy mode. ATS and the origin server are
all on the same host/IP.
If I understand things correctly, I shouldn't be using ATS unless it's the
one that has ALL the SSL certificates in a chain (instead of Apache having
the individual ones) and doing the remapping to the origin server, right?
So I am off to a false start as no caching will be done by ATS, I think.


On Sun, Jan 21, 2024 at 7:28 PM Leif Hedstrom <zw...@apache.org> wrote:

> 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 Sun, Jan 21, 2024 at 09:19 Odhiambo Washington <odhia...@gmail.com>
> wrote:
>
>> Thank you very much for the response.
>> I am going to use `traffic_ctl config defaults` to dump the defaults to a
>> file and compare with the documentation.
>>
>> Allow me to ask a related (newbie) question if you do not mind. I have my
>> Webserver configured in a way that any requests to http://site.name and
>> automatically redirected/rewritten to https://site.name (80 -> 443)
>> I host several sites all of which have their own SSL certificates from
>> Letsencrypt.
>> I am wondering how to handle this via the ATS.
>> Are there any examples I can use for remap.config
>>
>>
>> On Sun, Jan 21, 2024 at 7:07 PM Nick Dunkin <nick.dun...@vecima.com>
>> wrote:
>>
>>> Hi
>>>
>>> A config parameter that is absent from records.config will take its
>>> documented default value.  This way you can keep your records.config
>>> concise.
>>>
>>> Thanks
>>>
>>> Nick
>>>
>>> Sent from my iPhone
>>>
>>> On Jan 21, 2024, at 3:21 AM, Odhiambo Washington <odhia...@gmail.com>
>>> wrote:
>>>
>>> 
>>>
>>> CAUTION: This email originated from outside of the organization. Do not
>>> click links or open attachments unless you recognize the sender and know
>>> the content is safe.
>>>
>>>
>>> Hi,
>>>
>>> I am new here so please bear with me :)
>>> I am working on running ATS on FreeBSD and slowly going through the
>>> documentation.
>>> Because I have installed 9.2.1, I am reading the documentation at
>>> https://docs.trafficserver.apache.org/en/9.2.x/admin-guide/configuration/cache-basics.en.html
>>> <https://protect.checkpoint.com/v2/___https://docs.trafficserver.apache.org/en/9.2.x/admin-guide/configuration/cache-basics.en.html___.YzJ1OnZlY2ltYW5ldHdvcmtzOmM6bzo0OTY3YmFiZWQyZDI1MzBjMjE2ZWMxYWZmNGM1YTUxYzo2OjJkY2I6ODI3OTVmMmIyMGZlNzFkMTI4MmJiNWY1MDYzZWJmOWUyMjk4M2Q0MzU1MTkyZmFiMDFhMTA1OTMwNjQwZWU2NjpoOlQ>
>>> I have however encountered an issue where a certain config variable is
>>> documented, but missing from the sample configuration provided for
>>> records.config:
>>>
>>> The
>>> https://docs.trafficserver.apache.org/en/9.2.x/admin-guide/configuration/cache-basics.en.html#configuring-traffic-server-to-honor-client-no-cache-headers
>>> <https://protect.checkpoint.com/v2/___https://docs.trafficserver.apache.org/en/9.2.x/admin-guide/configuration/cache-basics.en.html%23configuring-traffic-server-to-honor-client-no-cache-headers___.YzJ1OnZlY2ltYW5ldHdvcmtzOmM6bzo0OTY3YmFiZWQyZDI1MzBjMjE2ZWMxYWZmNGM1YTUxYzo2OmFkMDE6MGUyZGRhNzY3ODI0ZDc2MDI2YmJlNzJlNDIyNmQ3ZDgwZTRlMDE3YjhlZjI5OTc3NDlkYzVhOGJiN2M4Zjk1MTpoOlQ>
>>> refers to the variable:
>>>
>>> proxy.config.http.cache.ignore_client_no_cache
>>>
>>> And that variable is missing from records.config. The same applies to
>>>
>>> proxy.config.http.cache.ignore_server_no_cache
>>>
>>> The docs for 9.2.1 above look like they are very similar to
>>> https://docs.trafficserver.apache.org/en/latest/admin-guide/configuration/cache-basics.en.html
>>> <https://protect.checkpoint.com/v2/___https://docs.trafficserver.apache.org/en/latest/admin-guide/configuration/cache-basics.en.html___.YzJ1OnZlY2ltYW5ldHdvcmtzOmM6bzo0OTY3YmFiZWQyZDI1MzBjMjE2ZWMxYWZmNGM1YTUxYzo2OjU2ODM6OWE5ZTQ4YmU5MWE0MTQ2MTY5MTY5ZjI1ZmMyNWNmMjlhNDMzODQ4OGEwNWYzM2E3YjllZGQ3MTIyYTRmOTcwZTpoOlQ>
>>> .
>>>
>>> Do I attribute this to the package maintainer's oversight and just add
>>> them somewhere within the file?
>>> The sample file is so well-documented though.
>>>
>>> Thank you.
>>>
>>> --
>>> Best regards,
>>> Odhiambo WASHINGTON,
>>> Nairobi,KE
>>> +254 7 3200 0004/+254 7 2274 3223
>>>  In an Internet failure case, the #1 suspect is a constant: DNS.
>>> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
>>> [How to ask smart questions:
>>> http://www.catb.org/~esr/faqs/smart-questions.html
>>> <https://protect.checkpoint.com/v2/___http://www.catb.org/~esr/faqs/smart-questions.html___.YzJ1OnZlY2ltYW5ldHdvcmtzOmM6bzo0OTY3YmFiZWQyZDI1MzBjMjE2ZWMxYWZmNGM1YTUxYzo2OjYwNDY6ZDNlMTU2NjI0MWMwZjFkMTc1NjIyN2RiZTcwN2JiZjdjNjU5ZGNmNjg2NTY0YWZmNmI0MTAyZGYwZTQ0OWY3ODpoOlQ>
>>> ]
>>>
>>>
>>
>> --
>> Best regards,
>> Odhiambo WASHINGTON,
>> Nairobi,KE
>> +254 7 3200 0004/+254 7 2274 3223
>>  In an Internet failure case, the #1 suspect is a constant: DNS.
>> "Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
>> [How to ask smart questions:
>> http://www.catb.org/~esr/faqs/smart-questions.html]
>>
>

-- 
Best regards,
Odhiambo WASHINGTON,
Nairobi,KE
+254 7 3200 0004/+254 7 2274 3223
 In an Internet failure case, the #1 suspect is a constant: DNS.
"Oh, the cruft.", egrep -v '^$|^.*#' ¯\_(ツ)_/¯ :-)
[How to ask smart questions:
http://www.catb.org/~esr/faqs/smart-questions.html]

Reply via email to