Return-Path: X-Original-To: apmail-trafficserver-users-archive@www.apache.org Delivered-To: apmail-trafficserver-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E0FA617BBB for ; Tue, 21 Oct 2014 00:07:38 +0000 (UTC) Received: (qmail 51999 invoked by uid 500); 21 Oct 2014 00:07:38 -0000 Delivered-To: apmail-trafficserver-users-archive@trafficserver.apache.org Received: (qmail 51934 invoked by uid 500); 21 Oct 2014 00:07:38 -0000 Mailing-List: contact users-help@trafficserver.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@trafficserver.apache.org Delivered-To: mailing list users@trafficserver.apache.org Received: (qmail 51925 invoked by uid 99); 21 Oct 2014 00:07:38 -0000 Received: from mail-relay.apache.org (HELO mail-relay.apache.org) (140.211.11.15) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Oct 2014 00:07:38 +0000 Received: from [17.149.234.65] (unknown [17.149.234.65]) by mail-relay.apache.org (ASF Mail Server at mail-relay.apache.org) with ESMTPSA id AC0CD1A02FC for ; Tue, 21 Oct 2014 00:07:16 +0000 (UTC) Content-Type: text/plain; charset=us-ascii Mime-Version: 1.0 (Mac OS X Mail 8.0 \(1990.1\)) Subject: Re: ATS not caching anything? From: James Peach In-Reply-To: Date: Mon, 20 Oct 2014 17:07:36 -0700 Content-Transfer-Encoding: quoted-printable Message-Id: References: To: users@trafficserver.apache.org X-Mailer: Apple Mail (2.1990.1) On Oct 20, 2014, at 5:01 PM, J David wrote: >=20 > Hello all, >=20 > After taking some first steps into ATS as a potential replacement for > an aging squid reverse proxy infrastructure, things appear to be going > mostly pretty well. The first test server is at least up and running, > and with a one-line remap.config, is able to properly handle requests. >=20 > However, it does not appear to be caching anything. The Age: header > is always 0, and the Via: header (with appropriate verbosity) reports > [cMsSf ]. With debugging logs turned on, confirmation appears in the > traffic.out log: >=20 > [Oct 20 23:25:43.146] Server {0x803808c00} DEBUG: (http) [88] > perform_cache_write_action CACHE_DO_NO_ACTION >=20 >=20 > The origin server is serving an ancient static text file: >=20 > HTTP/1.1 200 OK >=20 > Date: Mon, 20 Oct 2014 23:56:14 GMT >=20 > Server: Apache/2.2 >=20 > Last-Modified: Sat, 02 Dec 2006 08:09:00 GMT >=20 > ETag: "b543-7e-4239aa1015f00" >=20 > Accept-Ranges: bytes >=20 > Content-Length: 126 >=20 > Connection: close >=20 > Content-Type: text/html >=20 >=20 > That should be the very soul of cachability, but for some reason it > isn't. Why not? You probably need to set proxy.config.http.cache.required_headers ... = https://trafficserver.readthedocs.org/en/latest/reference/configuration/re= cords.config.en.html#proxy-config-http-cache-required-headers >=20 > The cache is configured with 32GiB of RAM and 32GiB of disk (but > ideally I would like to disable the disk cache entirely, ala squid's > "cache_dir null /null" setting, and cache entirely from RAM). The > cache appears to be working, as diags.log reports: >=20 > [Oct 20 23:12:04.608] Server {0x803809400} NOTE: cache enabled Pretty sure you can't disable the disk cache. Objects only get pulled = into RAM after coming through the disk cache J=