Apigee Edge Micro support for X-Forwarded-Proto

Not applicable

I how do I get Apigee Edge Micro to include the X-Forwarded-Proto? Just adding the value in the yaml doesn't work.

Example:

headers:
x-forwarded-proto: true

0 13 485
13 REPLIES 13

Hey devingrant

Are you looking for the proxy to populate this header?

-Matt

Hey devingrant,

I realized my question is weird.

Unfortunately that appears to be a bug. I'll file something, and take it from there. Stay tuned to this thread to know when the fix drops.

-Matt

We've got a candidate for a fix that will go into the next code push of edgemicro:

https://github.com/apigee/microgateway-core/pull/47

-Matt

will it also included the fix for the 'undefined' as a prefix in the x-forwarded-host?

I'm not familiar with that issue. Is there a community post that refers to it?

-Matt

Ah. It would appear there was a fix already deployed. Is this behavior still cropping up for you in edgemicro?

Here is the relevant pull request with the fix in question.

https://github.com/apigee/microgateway-core/pull/12

-Matt

Hey devingrant,

Few questions:

  1. Can you give me steps to reproduce the behavior you're seeing?
  2. What version of edgemicro are you using?

Unfortunately I don't see any updates in the other community post as to what the issue is. The last post I see on there is that a merged fix was linked in the last post.

-Matt

I am using edgemicro@2.0.0.

Btw, I am running it in a docker container using the ndietz/emgw image.

Is there any plans to officially provide a docker container in hub.docker.com?

We'll look to craft an officially support image soon. Stay tuned for that.

The current version of edgemicro you're using is actually pretty old. Our latest it 2.3.3-beta.

The x-forwarded-proto change will drop in the release that removes the beta tag.

This is in the latest release of EM 2.3.3