-
Notifications
You must be signed in to change notification settings - Fork 445
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
X-Forwarded-Host header missing in dotnet 8 isolated #10253
Comments
@paulverbeke are you using the ASP.NET Core integration for your tests? In the HTTP proxying mode, all headers should be forwarded and will be processed by the worker. |
@fabiocav thanks for getting back quickly. Yes we are using ASP.NET Core integration. But I couldn't find anything online regarding "HTTP proxying mode". Is there something I need to enable or specify somewhere ? EDIT: I just tested the starting Azure Functions template without ASP.NET Core integration (with HttpRequestData/HttpResponseData) and the header is available. |
@fabiocav are there any updates on this? I'm also experiencing the same issue |
I'm also encountering this issue with my migration from .net 6 in process to .net isolated. |
The X-Forwarded-Host header provided by Azure Front Door is missing in a fresh new function in dotnet 8 isolated.
Is working fine in dotnet 6 in-process but stops working when migrating to 8 isolated.
Investigative information
Please provide the following:
Repro steps
testforwardheader
, output the value of the header X-Forwarded-Hostreq.Headers.TryGetValue("X-Forwarded-Host", out StringValues value)
subdomain.myfrontdoordomain.com/myfunction
.subdomain.myfrontdoordomain.com/myfunction/api/testforwardheader
Expected behavior
in step 4 you should get the host requested by client, so
subdomain.myfrontdoordomain.com
Actual behavior
in step 4 you get an empty string
Known workarounds
Someone found a workaround. They were able to find and restore the value from the bindingContext.BindingData using custom middleware.
Workaround
Related information
written in C#
Someone else had this problem
The text was updated successfully, but these errors were encountered: