Even without the NGINX Filters Policy in the policy chain, APIcast 2.11+ forwards the If- and Range headers:
$ curl "localhost:8080/echo/test?user_key=debug" -H "If-None-Match: anything" -H "If-Match: something" -H "Range: test" { "method": "GET", "path": "/test", "args": "user_key=debug", "headers": { "HTTP_HOST": "echo-api.3scale.net", "HTTP_X_REAL_IP": "127.0.0.1", "HTTP_IF_NONE_MATCH": "anything", "HTTP_IF_MATCH": "something", "HTTP_RANGE": "test", "HTTP_X_FORWARDED_PROTO": "https", <other headers removed> } }
The tests are invalid because the 412 response they rely on actually comes from the upstream echo API.
We know these headers were not passed to upstream in 2.10 so possibly this is affected by a change in OpenResty/NGINX from 2.10 to 2.11 or by some other change in our code. We need to investigate whether this policy has any use cases.
- blocks
-
THREESCALE-8405 NGINX Filter policy is not available in 3scale SaaS
-
- Closed
-