x-forwarded-port makes little sense

[akrabat]

Given that I have an API gateway set up like this: wsk api create /base /test GET test -n testapi --response-type http, then I can access it like this:

$ curl https://service.eu.apiconnect.ibmcloud.com/gws/apigateway/api/2fb...be1/base/test

Inspecting __ow_headers, I find this:

"x-forwarded-url": "https://service.eu.apiconnect.ibmcloud.com/gws/apigateway/api/2fb...be1/base/test",
"x-forwarded-port": "8080",

The URL is correct, but the port should be 443.

[mhamann]

@akrabat in your opinion, should we just remove the x-forwarded-port header?

[akrabat]

I think that x-forwarded-port should be correct.

[rabbah]

443 in this case.