-
Notifications
You must be signed in to change notification settings - Fork 866
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
Proxy adds standard headers related to request forwarding #13
Comments
Planning notes: We need a minimal implementation of this for preview1. E.g. automatically append forwarders without any configurability. |
I can help with the minimal implementation. I already have it coded up to append Because of possible URL transformations, we also add a non-standard header with the full original incoming url. |
I did the minimal work for preview1 in #133. Moving this out of the preview1 milestone for further development. |
Design: I expect this to overlap heavily with the request transformation infrastructure we're designing in #21. We wouldn't necessarily ask you to define these headers in config (though nginx does), but we would use the same infrastructure to actually do the transformations. |
Yes this does align with the transforms, but we don't need another middleware to add transforms per request. We can pre build the transforms when building the config for each route/backend, then we can run them per request with minimal overhead. |
I think you should also consider supporting |
@damianh PathBase makes sense, you can't properly generate public urls without it. We do something like this for IIS-out-of-proc but at startup rather than per-request. |
@Tratcher Yes am aware of the at-startup approach, however I am suggesting per-request should be supported. |
@damianh sending x-forwarded-PathBase was implemented in YARP as part of #225. Filed dotnet/aspnetcore#23263 for receiving it. |
Excellent! |
The text was updated successfully, but these errors were encountered: