Skip to content
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.

Sign up for GitHub

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

Jump to bottom

[new feature] Support for using a custom header in request routing #16

Open
foxish opened this issue Jun 20, 2023 · 0 comments
Open

[new feature] Support for using a custom header in request routing #16

foxish opened this issue Jun 20, 2023 · 0 comments
Labels
platform

Comments

@foxish
Copy link
Member

foxish commented Jun 20, 2023

New feature or functionality
What would you like Signadot to do?

While OTel headers (baggage and tracestate) are the standardized method of propagating request metadata, there are some cases where a different header is already propagated through the application. While these applications are modified over time to use the OTel headers, the ability to route using a custom header can be useful in the interim period.

Additional considerations
Anything in particular to think about regarding this new feature?
@foxish foxish changed the title [new feature] Support for using a custom header in context propagation [new feature] Support for using a custom header in request routing Jun 20, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
platform
Projects
Signadot Public Roadmap
Status: Under Consideration
Milestone
No milestone
Development

No branches or pull requests
1 participant
@foxish