I've added on one of my API resource a parameter of type Header named Authorization. When trying to use it on the devportal this header is never sent when using the try out with a value on this header... It looks like this issue is only existing for this specific Header parameter "Authorization", if I do the same with another Header parameter name, it works.
Steps to reproduce:
On the publisher :
Create an new API
In "Runtime Configuration" :
Activate Oauth2, Basic Auth and API Key security
Replace the default Authorization Header in "Application Level Security" by something like "AuthorizationWSO2"
Add a new resource API with Security activated
Add parameter type "Header" with name "Authorization"
On devportal :
On Try Out, try to make a call to the resource with a value on the Header Parameter using an API Key
The Authorization parameter will never be send if you check on the network console and the curl example will not diplay it
If you add another Header parameter named for example "HeaderTest", and you try again, this one will be send and display on the curl sample...
Description:
I've added on one of my API resource a parameter of type Header named Authorization. When trying to use it on the devportal this header is never sent when using the try out with a value on this header... It looks like this issue is only existing for this specific Header parameter "Authorization", if I do the same with another Header parameter name, it works.
Steps to reproduce:
On the publisher :
On devportal :
If you add another Header parameter named for example "HeaderTest", and you try again, this one will be send and display on the curl sample...
Affected Product Version:
API Manager 3.1.0
Regards, Jérôme.