Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

How are vary headers treated? #5

Open
@hedleyroos

Description

I have a scenario where the upstream server (in this case Django) may set a few vary headers. I do ignore Set-Cookie in the Nginx configuration.

  1. Visit /path/ from a web browser -> creates a file in the cache directory.
  2. Visit same /path/ with curl -X GET from a command line on the webserver -> creates another file in the cache directory.

I assume this is because of different Accept-Encoding's and I understand the reasoning.

Now, when I issue curl -X PURGE http://localhost/path/ only the cached file from (2) is deleted.

Is there a way to tell the module to consider only the cache key, no other headers, when determining which cached files to delete?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions

        AltStyle によって変換されたページ (->オリジナル) /