-
Notifications
You must be signed in to change notification settings - Fork 89
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
Use protocol default port in the event that no port is provided in host #228
Conversation
Thank you, this change means that the host port won't be converted to the underlying transport port. I feel we are still missing a piece when it comes to load balancers and identifying x-forward-for headers, but outside the scope of this discussion and probably this library. I will test this on my side in the next couple of days. |
I got some help from an editor of RFC 9110 after asking for some support about the topic, clarifying a bit 🤷🏻 |
@yordis we have pretty comprehensive coverage of absolute URIs ( bandit/test/bandit/http1/request_test.exs Lines 195 to 254 in de17595
bandit/test/bandit/http2/protocol_test.exs Lines 2131 to 2237 in de17595
I've re-read the relevant spec links above a few times over the last couple of days and this is sitting better and better with me. Quite confident we're doing it right here. |
Fixes #106
Relevant to your interests @wkirschbaum