Rate limiting didn't disable with boolean in 4.3.x
avoidwork opened this issue · 0 comments
avoidwork commented
I shouldn't have seen a set of rate limit headers in the following response:
kuma:~ jamullig$ curl -i -X HEAD https://parking.corp.adobe.com
Warning: Setting custom HTTP method to HEAD with -X/--request may not work the
Warning: way you want. Consider using -I/--head instead.
HTTP/1.1 200 OK
server: tenso/4.3.21
x-powered-by: node.js/6.9.5
allow: GET, HEAD, OPTIONS
x-frame-options: SAMEORIGIN
strict-transport-security: max-age=10886400; includeSubDomains; preload
x-ratelimit-limit: 50
x-ratelimit-remaining: 49
x-ratelimit-reset: 1486480307
accept-ranges: bytes
content-type: text/html; charset=utf-8
cache-control: no-cache
connection: close
content-length: 0
x-response-time: 0.52 ms
set-cookie: connect.sid=abc; Path=/; HttpOnly
Date: Tue, 07 Feb 2017 15:09:47 GMT