You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@trafficserver.apache.org by "Leif Hedstrom (JIRA)" <ji...@apache.org> on 2011/05/18 23:10:47 UTC

[jira] [Updated] (TS-790) Even with negative caching disable, we end up caching 40x responses for 1800 seconds.

     [ https://issues.apache.org/jira/browse/TS-790?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Leif Hedstrom updated TS-790:
-----------------------------

      Component/s:     (was: Clustering)
                   Core
    Fix Version/s: 2.1.9
         Assignee: Leif Hedstrom
          Summary: Even with negative caching disable, we end up caching 40x responses for 1800 seconds.  (was: With clustering enabled we cache negative responses regardless of configuration)

It seems this happens without clustering too, so moving this to v2.1.9

> Even with negative caching disable, we end up caching 40x responses for 1800 seconds.
> -------------------------------------------------------------------------------------
>
>                 Key: TS-790
>                 URL: https://issues.apache.org/jira/browse/TS-790
>             Project: Traffic Server
>          Issue Type: Bug
>          Components: Core
>    Affects Versions: 2.1.8
>            Reporter: Leif Hedstrom
>            Assignee: Leif Hedstrom
>             Fix For: 2.1.9
>
>
> It seems with clustering enabled, we end up caching negative responses (e.g. 404) for 1800s (which is the default in RecordsConfig.cc), even when negative caching is disabled.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira