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.

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

Support setting headers like Allow, Supported #141

Open
emiago opened this issue Oct 18, 2024 · 2 comments
Open

Support setting headers like Allow, Supported #141

emiago opened this issue Oct 18, 2024 · 2 comments

Comments

@emiago
Copy link
Owner

emiago commented Oct 18, 2024

more related on this PR #140

We could potentially have this headers or behavior part of client or server.

Ex server could detect what methods are supported and if caller wants those values could be passed on response.

Avoiding implicit behavior is desirable.

@SilvaMendes
Copy link

The idea would be to maintain compatibility of what the endpoint offers via header between peers, but it would be the server's responsibility to define whether the methods are supported or not, if not supported it would remove it from the response or even from the forwarding.

@emiago
Copy link
Owner Author

emiago commented Oct 22, 2024

hey @SilvaMendes I suggest exploring this more from server API then. As in some cases I used this API to build that headers.
Checkout RegisteredMethods .
Unfortunately I think we would need better middleware implementation for supporting this.
For now I think it is on Caller user to build custom reply wrapper that inject this headers.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants