Welcome! Log In Create A New Profile

Advanced

Re: Throttle requests with limit_req rate based on header from response to auth subrequest

August 30, 2018 07:47PM
Digging into this some more today, I've continued to find what seems to be odd behavior. If I remove all of the limit_req directives, then the mapped variables based on the upstream are always present:

{

"upstream_http_tier": "",
"tier": "02x",
"http_tier": "",
"key_two": "",
"key_three": "",
"key_two_from_upstream": "match",
"key_three_from_upstream": "nonempty",
}

Whereas if I add the limit_req directives that reference "key_*" back in, then those keys are no longer populated correctly:

{

"upstream_http_tier": "",
"tier": "02x",
"http_tier": "",
"key_two": "",
"key_three": "",
"key_two_from_upstream": "",
"key_three_from_upstream": "",
}
Subject Author Posted

Throttle requests with limit_req rate based on header from response to auth subrequest

jarstewa August 29, 2018 07:13PM

Re: Throttle requests with limit_req rate based on header from response to auth subrequest

Francis Daly August 30, 2018 04:10AM

Re: Throttle requests with limit_req rate based on header from response to auth subrequest

jarstewa August 30, 2018 12:53PM

Re: Throttle requests with limit_req rate based on header from response to auth subrequest

jarstewa August 30, 2018 07:47PM

Re: Throttle requests with limit_req rate based on header from response to auth subrequest

jarstewa August 30, 2018 08:13PM

Re: Throttle requests with limit_req rate based on header from response to auth subrequest

Francis Daly August 31, 2018 07:10AM



Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 69
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready