-
Notifications
You must be signed in to change notification settings - Fork 170
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Debug header does not work #216
Comments
Another affected field is: configuration.version |
I'm thinking about how to get rid of the provider key in the debug header. One of the options is to have different debug header for each service I'm considering the service token. It is already there and users already have access to it. So it kind of feels like natural way to have per service secret for the debug header. Wdyt? |
The problem is that if you have multiple services configured, it would be a bit hard to know what service the request will be mapped to (especially when using path-based routing). I know that we are planning to remove the provider key from the JSON spec, but I don't know what would be a reasonable alternative :/ |
@mayorova I'd consider it almost a feature. If you get the header back when using path based routing, you know it routed right :) |
When the
X-3scale-debug
header with the provider key as its value is sent to the APIcast, it should add the debug headers with the response.This was broken after splitting the configuration, as
_M.configuration.debug_header
does not exist, as it's referring toconfiguration_store.lua
and notconfiguration.lua
as before.The text was updated successfully, but these errors were encountered: