api-components-bundle/features/main/cache_headers.feature at a9f7b18cd76e0874bba7b4a07f539af98ef54dcf · components-web-app/api-components-bundle · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
Feature: Cache-safety headers so shared caches can distinguish public from personalised responses
  In order for CDNs, reverse proxies and service workers to cache API responses safely
  As a consumer of the API
  I need authenticated responses on affected resource types marked non-cacheable, while public
  responses and unaffected resource types stay cacheable

  Background:
    Given I add "Accept" header equal to "application/ld+json"
    And I add "Content-Type" header equal to "application/ld+json"

  @loginAdmin
  Scenario Outline: Authenticated GETs of affected resource types are marked non-cacheable
    Given <setup>
    When <request>
    Then the response status code should be 200
    And the header "Cache-Control" should contain "private"
    And the header "Cache-Control" should contain "no-store"
    Examples:
      | setup                                                                                    | request                                                        |
      | there is a Route "/contact" with a page                                                  | I send a "GET" request to "/_/routes//contact"                 |
      | there is a PageData resource with the route path "/my-route"                             | I send a "GET" request to "/_/resource_manifest//my-route"     |
      | there is a ComponentGroup with 1 components                                              | I send a "GET" request to the resource "position_0"            |
      | there is a published resource with a draft set to publish at "2999-12-31T23:59:59+00:00" | I send a "GET" request to the resource "publishable_published" |

  Scenario Outline: Anonymous GETs of affected resource types stay publicly cacheable
    Given <setup>
    When <request>
    Then the response status code should be 200
    And the header "Cache-Control" should contain "public"
    And the header "Cache-Control" should not contain "no-store"
    Examples:
      | setup                                                        | request                                                    |
      | there is a Route "/contact" with a page                      | I send a "GET" request to "/_/routes//contact"             |
      | there is a PageData resource with the route path "/my-route" | I send a "GET" request to "/_/resource_manifest//my-route" |
      | there is a ComponentGroup with 1 components                  | I send a "GET" request to the resource "position_0"        |

  @loginAdmin
  Scenario: An authenticated GET of an unaffected resource type stays publicly cacheable
    Given there is a Layout
    When I send a "GET" request to the resource "layout"
    Then the response status code should be 200
    And the header "Cache-Control" should contain "public"
    And the header "Cache-Control" should not contain "no-store"