opened
nynymike
username_0
I was talking to a customer, and they pointed out that in some cases the URL may be the same, but the version of the API may be passed as a header parameter. In this case, we may want to configure different OAuth/UMA scopes. I think we should implement this feature in both the backend and GUI.
API Version in Headers
issue
created
altexy
username_1
OK, @username_0  I will research this topic asap
comment
created
altexy
username_1
https://github.com/Kong/kong/issues/505#issuecomment-362666313
comment
created
altexy
username_1
I don't think it is a good idea to add such layer into our plugins.
By Kong philosophy `different OAuth/UMA scopes` means the different plugin configurations.
So we need to be able to configure our plugin for the same hosts/methods/paths, but also by request header.
comment
created
altexy
username_1
@username_0 
It may be a time-consuming project to add such a feature into upstream Kong.
We will need to follow all Kong rules, write tests.
I see a lot of complaints about the difficulty to reproduce Kong development environment.

At the moment we have next answer:

When Kong will support Route per arbitrary request header - we will be able to do it without any changes on plugin side. Maybe will need some GUI work.
comment
created
nynymike
username_0
Ok. I didn't have it as an immediate requirement. We can keep an eye on it and guage demand.
comment
created
ldeveloperl1985
username_2
I think kong header filter feature is covered this issue https://docs.konghq.com/1.3.x/proxy/#request-headers-except-host
@username_1  Please check  and confirm
comment
created
altexy
username_1
Agree, Kong 1.3 does support header-based routing
comment
closed
altexy
username_1
issue