@toa.io/extensions.exposition 1.0.0-alpha.22 → 1.0.0-alpha.220

package/features/cache.feature

@@ -1,3 +1,4 @@
+@security
 Feature: Caching
 
   Background:
@@ -10,6 +11,40 @@ Feature: Caching
       | _id                              | identity                         | role      |
       | 775a648d054e4ce1a65f8f17e5b51803 | b70a7dbca6b14a2eaac8a9eb4b2ff4db | developer |
 
+  Scenario: Default caching
+    Given the annotation:
+      """yaml
+      /:
+        anonymous: true
+        GET:
+          dev:stub: foo
+        /private:
+          auth:role: developer
+          GET:
+            dev:stub: bar
+      """
+    When the following request is received:
+      """
+      GET / HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the reply does not contain:
+      """
+      cache-control:
+      """
+    When the following request is received:
+      """
+      GET /private/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      cache-control: no-store
+      """
+
   Scenario: Caching successful response
     Given the annotation:
       """yaml
@@ -195,8 +230,8 @@ Feature: Caching
 
   Scenario: Private responses are sent with `vary: authorization`
     Given the `identity.basic` database contains:
-      | _id                              | username  | password                                                     |
-      | efe3a65ebbee47ed95a73edd911ea328 | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+      | _id                              | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
     And the annotation:
       """yaml
       /:
@@ -205,6 +240,10 @@ Feature: Caching
           cache:control: max-age=10000
           GET:
             dev:stub: Keep it
+        /sessions/:id:
+          auth:id: id
+          GET:
+            dev:stub: Keep it
       """
     When the following request is received:
       """
@@ -212,7 +251,6 @@ Feature: Caching
       host: nex.toa.io
       authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
       """
-    # `no-store` when token is issued
     Then the following reply is sent:
       """
       200 OK
@@ -231,3 +269,54 @@ Feature: Caching
       cache-control: private, max-age=10000
       vary: authorization
       """
+    When the following request is received:
+      """
+      GET /sessions/efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Token ${{ token }}
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      cache-control: private
+      vary: authorization
+      """
+
+  Scenario: Authenticated `no-cache` responses
+    Given the `identity.basic` database contains:
+      | _id                              | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+    And the annotation:
+      """yaml
+      /:
+        /:id:
+          auth:id: id
+          cache:control: no-cache
+          GET:
+            dev:stub: Keep it
+      """
+    When the following request is received:
+      """
+      GET /efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
+      """
+    # no-store since the response contains the token
+    Then the following reply is sent:
+      """
+      200 OK
+      authorization: Token ${{ token }}
+      cache-control: no-store
+      """
+    When the following request is received:
+      """
+      GET /efe3a65ebbee47ed95a73edd911ea328/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Token ${{ token }}
+      """
+    # private is added since the response is authenticated
+    Then the following reply is sent:
+      """
+      200 OK
+      cache-control: private, no-cache
+      """

package/features/cors.feature

@@ -1,6 +1,7 @@
+@security
 Feature: CORS Support
 
-  Scenario: Using CORS
+  Scenario: Basic CORS permissions
     Given the annotation:
       """yaml
       /:
@@ -19,8 +20,8 @@ Feature: CORS Support
       """
       204 No Content
       access-control-allow-origin: https://hello.world
-      access-control-allow-methods: GET, POST, PUT, PATCH, DELETE
-      access-control-allow-headers: accept, authorization, content-type, etag, if-match, if-none-match
+      access-control-allow-methods: GET, POST, PUT, PATCH, DELETE, LOCK, UNLOCK
+      access-control-allow-headers: accept, authorization, content-type, if-match, if-none-match
       access-control-allow-credentials: true
       access-control-max-age: 3600
       cache-control: max-age=3600
@@ -36,11 +37,31 @@ Feature: CORS Support
       """
       200 OK
       access-control-allow-origin: https://hello.world
-      access-control-expose-headers: authorization, content-type, content-length, etag
+      access-control-allow-credentials: true
+      access-control-expose-headers: authorization, content-type, content-length, date, etag, last-modified
+      vary: origin
+      """
+
+  Scenario: Always vary CORS
+    Given the annotation:
+      """yaml
+      /:
+        anonymous: true
+        GET:
+          dev:stub: hello
+      """
+    When the following request is received:
+      """
+      GET / HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the following reply is sent:
+      """
+      200 OK
       vary: origin
       """
 
-  Scenario: Errors contain CORS headers
+  Scenario: Errors have CORS headers
     Given the annotation:
       """yaml
       /:
@@ -58,7 +79,7 @@ Feature: CORS Support
       """
       404 Not Found
       access-control-allow-origin: https://hello.world
-      access-control-expose-headers: authorization, content-type, content-length, etag
+      access-control-expose-headers: authorization, content-type, content-length, date, etag, last-modified
       vary: origin
       """
     When the following request is received:
@@ -71,6 +92,6 @@ Feature: CORS Support
       """
       401 Unauthorized
       access-control-allow-origin: https://hello.world
-      access-control-expose-headers: authorization, content-type, content-length, etag
+      access-control-expose-headers: authorization, content-type, content-length, date, etag, last-modified
       vary: origin
       """

package/features/debug.feature

@@ -0,0 +1,34 @@
+Feature: Debugging
+
+  Scenario: Operation call
+    Given the `identity.basic` database contains:
+      | _id                              | authority | username  | password                                                     |
+      | efe3a65ebbee47ed95a73edd911ea328 | nex       | developer | $2b$10$ZRSKkgZoGnrcTNA5w5eCcu3pxDzdTduhteVYXcp56AaNcilNkwJ.O |
+    And the `identity.roles` database contains:
+      | _id                              | identity                         | role      |
+      | 775a648d054e4ce1a65f8f17e5b51803 | efe3a65ebbee47ed95a73edd911ea328 | developer |
+    And the annotation:
+      """yaml
+      debug: true
+      """
+    And the `greeter` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          auth:role: developer
+          io:output: true
+          GET: greet
+      """
+    When the following request is received:
+      """
+      GET /greeter/ HTTP/1.1
+      host: nex.toa.io
+      authorization: Basic ZGV2ZWxvcGVyOnNlY3JldA==
+      accept: text/plain
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      Hello
+      """

package/features/dev.feature

@@ -0,0 +1,87 @@
+Feature: Dev
+
+  Scenario: Delays
+    Given the annotation:
+      """yaml
+      /:
+        io:output: true
+        anonymous: true
+        dev:sleep: 3000
+        GET:
+          dev:stub: hello
+        /nested:
+          GET:
+            dev:stub: world
+      """
+    # CORS permission
+    When the following request is received:
+      """
+      OPTIONS / HTTP/1.1
+      origin: http://example.com
+      """
+    Then the following reply is sent:
+      """
+      204 No Content
+      access-control-allow-headers: accept, authorization, content-type, if-match, if-none-match, sleep
+      """
+    When the following request is received:
+      """
+      GET / HTTP/1.1
+      sleep: [1000, 2000]
+      """
+    # check the response time
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    When the following request is received:
+      """
+      GET /nested/ HTTP/1.1
+      sleep: [100, 300]
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    When the following request is received:
+      """
+      GET / HTTP/1.1
+      sleep: [1000, 3500]
+      """
+    Then the following reply is sent:
+      """
+      400 Bad Request
+
+      "Invalid sleep duration"
+      """
+
+  Scenario: Faulty mode
+    Given the annotation:
+      """yaml
+      /:
+        io:output: true
+        anonymous: true
+        dev:faulty: 1
+        GET:
+          dev:stub: hello
+      """
+    # CORS permission
+    When the following request is received:
+      """
+      OPTIONS / HTTP/1.1
+      origin: http://example.com
+      """
+    Then the following reply is sent:
+      """
+      204 No Content
+      access-control-allow-headers: accept, authorization, content-type, if-match, if-none-match, faulty
+      """
+    When the following request is received:
+      """
+      GET / HTTP/1.1
+      faulty: 1
+      """
+    Then the following reply is sent:
+      """
+      503 Service Unavailable
+      """

package/features/dynamic.feature

@@ -9,6 +9,7 @@ Feature: Dynamic tree updates
     Given the Gateway is running
     And the `pots` is running with the following manifest:
       """yaml
+      version: 1
       exposition:
         /:
           io:output: true
@@ -26,6 +27,45 @@ Feature: Dynamic tree updates
       """
     Then the `pots` is stopped
     Then the `pots` is running with the following manifest:
+      """yaml
+      version: 2
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+
+  Scenario: Repeat routes
+    Given the Gateway is running
+    And the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      """
+    Then the `pots` is stopped
+    And the `pots` is running with the following manifest:
       """yaml
       exposition:
         /:
@@ -46,6 +86,7 @@ Feature: Dynamic tree updates
   Scenario: Updating routes with conflict
     And the `pots` is running with the following manifest:
       """yaml
+      version: 1.0.0
       exposition:
         /:id:
           io:output: true
@@ -54,6 +95,7 @@ Feature: Dynamic tree updates
     Then the `pots` is stopped
     Then the `pots` is running with the following manifest:
       """yaml
+      version: 1.1.0
       exposition:
         /:
           io:output: true
@@ -79,6 +121,7 @@ Feature: Dynamic tree updates
   Scenario: Updating method mapping
     Given the `pots` is running with the following manifest:
       """yaml
+      version: a
       exposition:
         /big:
           io:output: true
@@ -90,6 +133,7 @@ Feature: Dynamic tree updates
     Then the `pots` is stopped
     Then the `pots` is running with the following manifest:
       """yaml
+      version: b
       exposition:
         /big:
           io:output: true

package/features/errors.feature

@@ -39,7 +39,7 @@ Feature: Errors
       404 Not Found
       content-type: application/json
 
-      "Trailing slash is required."
+      "Trailing slash is required"
       """
 
   Scenario: Missing method
@@ -110,7 +110,7 @@ Feature: Errors
       400 Bad Request
       content-type: text/plain
 
-      Query limit must be between 1 and 1000 inclusive.
+      Query limit must be between 1 and 100 inclusive
       """
 
   Scenario: Closed query criteria
@@ -121,7 +121,7 @@ Feature: Errors
           GET:
             endpoint: enumerate
             query:
-              criteria: temerature>60
+              criteria: temperature>60
       """
     When the following request is received:
       """
@@ -156,7 +156,7 @@ Feature: Errors
       400 Bad Request
       content-type: text/plain
 
-      Query must NOT have additional properties
+      Query Property foo is not expected to be here
       """
 
   Scenario: Malformed authorization header
@@ -176,7 +176,7 @@ Feature: Errors
       """
       401 Unauthorized
 
-      Malformed authorization header.
+      Malformed authorization header
       """
 
   Scenario Outline: Exception is thrown (debug: <debug>)
@@ -223,3 +223,15 @@ Feature: Errors
       """
       406 Not Acceptable
       """
+
+  Scenario: Not acceptable request with error
+    When the following request is received:
+      """
+      GET /robots.txt HTTP/1.1
+      host: nex.toa.io
+      accept: text/html
+      """
+    Then the following reply is sent:
+      """
+      404 Not Found
+      """

package/features/etag.feature

@@ -77,6 +77,114 @@ Feature: Optimistic concurrency control
       etag: "2"
       """
 
+  Scenario: Using etag with enumeration
+    Given the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          GET: enumerate
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: ${{ etag }}
+      """
+    When the following request is received:
+      """
+      GET /pots/ HTTP/1.1
+      host: nex.toa.io
+      if-none-match: ${{ etag }}
+      """
+    Then the following reply is sent:
+      """
+      304 Not Modified
+      etag: ${{ etag }}
+      """
+
+  Scenario: Weak `etag`
+    Given the `pots` is running with the following manifest:
+      """yaml
+      exposition:
+        /:
+          io:output: true
+          POST: create
+          /:id:
+            GET: observe
+            PUT: transit
+      """
+    When the following request is received:
+      """
+      POST /pots/ HTTP/1.1
+      host: nex.toa.io
+      accept: application/yaml
+      content-type: application/yaml
+
+      title: Hello
+      volume: 1.5
+      """
+    Then the following reply is sent:
+      """
+      201 Created
+      etag: "1"
+
+      id: ${{ id }}
+      """
+    When the following request is received:
+      """
+      GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "1"
+      """
+    When the following request is received:
+      """
+      GET /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      if-none-match: W/"1"
+      """
+    Then the following reply is sent:
+      """
+      304 Not Modified
+      etag: W/"1"
+      """
+    When the following request is received:
+      """
+      PUT /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      content-type: application/yaml
+      if-match: W/"38"
+
+      volume: 2.5
+      """
+    Then the following reply is sent:
+      """
+      412 Precondition Failed
+      """
+    When the following request is received:
+      """
+      PUT /pots/${{ id }}/ HTTP/1.1
+      host: nex.toa.io
+      content-type: application/yaml
+      if-match: W/"1"
+
+      volume: 2.5
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+      etag: "2"
+      """
+
   Scenario: Unexpected `if-match` format
     Given the `pots` is running with the following manifest:
       """yaml
@@ -99,5 +207,30 @@ Feature: Optimistic concurrency control
       """
       400 Bad Request
 
-      Invalid ETag.
+      Invalid ETag
+      """
+
+  Scenario: Etag with non-queryable operation
+    Given the `echo` is running with the following manifest:
+      """yaml
+      exposition:
+        /:foo/:id:
+          GET:
+            io:output: true
+            map:headers:
+              name: if-match
+            endpoint: affect
+      """
+    When the following request is received:
+      """
+      GET /echo/foo/Bob/ HTTP/1.1
+      host: nex.toa.io
+      accept: text/plain
+      if-match: "1"
+      """
+    Then the following reply is sent:
+      """
+      200 OK
+
+      Hello "1"
       """