Enable support like this Placeholders for X-Forwarded-Proto

[rocleegithub]

New Feature

Enable support like this Placeholders

"X-Forwarded-Proto": "{UpstreamForwardedProto}"

Enable support for this for some services

Thanks~

[raman-m]

Didn't you read Contributing rules in ReadMe.md?
You need to use Issue template to write the description!

Enable support like this Placeholders
"X-Forwarded-Proto": "{UpstreamForwardedProto}"

Could you provide more details of your idea please, and what's the final goal of your request?
What Ocelot feature is it related to?

Enable support for this for some services

What' services did you mean actually?

[rocleegithub]

Restore the original Request Scheme through Request.GetAbsoluteUri()

[raman-m]

Sorry, I don't understand you!

[rocleegithub]

like this proxy_set_header X-Forwarded-Proto $http_X_Forwarded_Proto??$scheme;

[raman-m]

We are discussing Headers Transformation and, in particular, Placeholders, correct? The currently implemented placeholders for forwarding include:

• {RemoteIpAddress}, which corresponds to HttpContext.Connection.RemoteIpAddress
• {UpstreamHost}, which is equivalent to HttpContext.Request.Headers.TryGetValue("Host", out var upstreamHost)

All placeholders versus headers are implemented in the Ocelot.Infrastructure.Placeholders class →

Ocelot/src/Ocelot/Infrastructure/Placeholders.cs

Line 9 in da9d6fa

public class Placeholders : IPlaceholders

---

"X-Forwarded-Proto": "{UpstreamForwardedProto}"

I've reviewed the Mozilla documentation and realized that the X-Forwarded-Proto header is not a standard one; internet tools use their own headers (refer to Examples). Therefore, we have a standardized header, which is Forwarded. It appears that you do not have this Forwarded header in downstreams, correct?

In conclusion,

it would be logical to include support for those headers; at the very least, we could treat the X-Forwarded-Proto header as a proprietary Ocelot header.
Would you be willing to initiate a pull request?