t/apicast-policy-headers: test push operation

Author: davidor

t/apicast-policy-headers.t

@@ -169,7 +169,87 @@ Existing-Header:
 --- no_error_log
 [error]
 
-=== TEST 3: 'set' operation in response headers
+=== TEST 3: 'push' operation in request headers
+We test 3 things:
+1) Push op with a header that does not exist, does not change anything.
+2) Push op with a header that exists, adds a new header with the same name and
+   the given value.
+3) Check that the headers are received in the upstream but not in the response
+   of the original request.
+--- configuration
+{
+  "services": [
+    {
+      "id": 42,
+      "backend_version":  1,
+      "backend_authentication_type": "service_token",
+      "backend_authentication_value": "token-value",
+      "proxy": {
+        "policy_chain": [
+          { "name": "apicast.policy.apicast" },
+          {
+            "name": "apicast.policy.headers",
+            "configuration":
+              {
+                "request":
+                  [
+                    { "op": "push", "header": "New-Header", "value": "config_value_nh" },
+                    { "op": "push", "header": "Existing-Header", "value": "config_value_eh" }
+                  ]
+              }
+          }
+        ],
+        "api_backend": "http://test:$TEST_NGINX_SERVER_PORT/",
+        "proxy_rules": [
+          { "pattern": "/", "http_method": "GET", "metric_system_name": "hits", "delta": 2 }
+        ]
+      }
+    }
+  ]
+}
+--- backend
+  location /transactions/authrep.xml {
+    content_by_lua_block {
+      local expected = "service_token=token-value&service_id=42&usage%5Bhits%5D=2&user_key=value"
+      local args = ngx.var.args
+      if args == expected then
+        ngx.exit(200)
+      else
+        ngx.log(ngx.ERR, expected, ' did not match: ', args)
+        ngx.exit(403)
+      end
+    }
+  }
+--- upstream
+  location / {
+     content_by_lua_block {
+       local existing_header_values = ngx.req.get_headers()['Existing-Header']
+
+       if ngx.req.get_headers()['New-Header'] then
+         ngx.log(ngx.ERR, "Received unexpected header New-Header")
+       elseif existing_header_values[1] ~= 'request_value_eh1' or
+           existing_header_values[2] ~= 'request_value_eh2' or
+           existing_header_values[3] ~= 'config_value_eh' then
+         ngx.log(ngx.ERR, "The header 'Existing-Header' does not have the correct value")
+       else
+         ngx.say('yay, api backend');
+       end
+     }
+  }
+--- request
+GET /?user_key=value
+--- more_headers
+Existing-Header: request_value_eh1
+Existing-Header: request_value_eh2
+--- response_body
+yay, api backend
+--- response_headers
+Existing-Header:
+--- error_code: 200
+--- no_error_log
+[error]
+
+=== TEST 4: 'set' operation in response headers
 We test 3 things:
 1) Set op with a header that does not exit creates it with the given value.
 2) Set op with a header that exists, clears it and sets the given value.
@@ -239,7 +319,7 @@ Header-To-Delete:
 --- no_error_log
 [error]
 
-=== TEST 4: 'add' operation in response headers
+=== TEST 5: 'add' operation in response headers
 We test 2 things:
 1) Add op with a header that does not exist creates it with the given value.
 2) Add op with a header that exists, creates a new header with the same name
@@ -307,7 +387,76 @@ Header-To-Delete:
 --- no_error_log
 [error]
 
-=== TEST 5: headers policy without a configuration
+=== TEST 6: 'push' operation in response headers
+We test 3 things:
+1) Push op with a header that does not exist, does not change anything.
+2) Push op with a header that exists, adds a new header with the same name and
+   the given value.
+3) Check that the headers are received in the upstream but not in the response
+   of the original request.
+--- configuration
+{
+  "services": [
+    {
+      "id": 42,
+      "backend_version":  1,
+      "backend_authentication_type": "service_token",
+      "backend_authentication_value": "token-value",
+      "proxy": {
+        "policy_chain": [
+          { "name": "apicast.policy.apicast" },
+          {
+            "name": "apicast.policy.headers",
+            "configuration":
+              {
+                "response":
+                  [
+                    { "op": "push", "header": "New-Header", "value": "config_value_nh" },
+                    { "op": "push", "header": "Existing-Header", "value": "config_value_eh" }
+                  ]
+              }
+          }
+        ],
+        "api_backend": "http://test:$TEST_NGINX_SERVER_PORT/",
+        "proxy_rules": [
+          { "pattern": "/", "http_method": "GET", "metric_system_name": "hits", "delta": 2 }
+        ]
+      }
+    }
+  ]
+}
+--- backend
+  location /transactions/authrep.xml {
+    content_by_lua_block {
+      local expected = "service_token=token-value&service_id=42&usage%5Bhits%5D=2&user_key=value"
+      local args = ngx.var.args
+      if args == expected then
+        ngx.exit(200)
+      else
+        ngx.log(ngx.ERR, expected, ' did not match: ', args)
+        ngx.exit(403)
+      end
+    }
+  }
+--- upstream
+  location / {
+     content_by_lua_block {
+       ngx.header['Existing-Header'] = 'upstream_value_eh'
+       ngx.say('yay, api backend')
+     }
+  }
+--- request
+GET /?user_key=value
+--- response_body
+yay, api backend
+--- response_headers
+Existing-Header: upstream_value_eh, config_value_eh
+New-Header:
+--- error_code: 200
+--- no_error_log
+[error]
+
+=== TEST 7: headers policy without a configuration
 Just to make sure that APIcast does not crash when the policy does not have a
 configuration.
 --- configuration