Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
erp5 erp5
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Labels
    • Labels
  • Merge requests 140
    • Merge requests 140
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Jobs
  • Commits
Collapse sidebar
  • nexedi
  • erp5erp5
  • Merge requests
  • !1398

Open
Created Apr 14, 2021 by Kazuhiko Shiozaki@kazuhikoOwner
  • Report abuse
Report abuse

WIP: make AcceleratedHTTPCacheManager effective only if object is directly published.

  • Overview 6
  • Commits 2
  • Changes 2

If we accidentally specify AcceleratedHTTPCacheManager in a widely-called Script (Python) by mistake (that happened in reality), many responses will have wrong Cache-Control header and it is very hard to recover if they are cached in each browser's cache.

With this change, AcceleratedHTTPCacheManager is effective only when the object itself is directly published, so that we can prevent such unexpected cache pollution.

/cc @romain @jerome @vpelletier @tb

Assignee
Assign to
Reviewer
Request review from
None
Milestone
None
Assign milestone
Time tracking
Source branch: limit_accelerated_http_cache_manager
GitLab Nexedi Edition | About GitLab | About Nexedi | 沪ICP备2021021310号-2 | 沪ICP备2021021310号-7