It's good practive to send a Retry-After header along with 429 (or 503) status. We can achieve this in Envoy by setting the following in the rate limit configuration:
enable_x_ratelimit_headers: DRAFT_VERSION_03
response_headers_to_add:
header:
key: Retry-After
value: "%RESP(x-ratelimit-reset)%"However, if we dobn't want the x-ratelimit-* headers to be present in the response, we will probably have to add another filter to remove them again. Or maybe there's another way to generate Retry-After?