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

Gateway docstrings do not specify behavior for when request hostname does not match any listener hostname. #3259

Open
briantkennedy opened this issue Aug 9, 2024 · 2 comments
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@briantkennedy
Copy link
Contributor

What would you like to be added:

The GatewaySpec.Listener docstring does not define behavior for when a request does not match any hostname defined in a Listener.

Why this is needed:

The only place this is defined is in a single conformance test:

Response: http.Response{StatusCode: 404},

@briantkennedy briantkennedy added the kind/documentation Categorizes issue or PR as related to documentation. label Aug 9, 2024
@Shridhar2104
Copy link

can I work on this issue ?

@shaneutt shaneutt added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Sep 20, 2024
@shaneutt
Copy link
Member

We'll need to triage this, and then if you're still interested in working on it we'll keep you in mind! Thank you for your interest keep subscribed to this issue for updates.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/documentation Categorizes issue or PR as related to documentation. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
Status: Triage
Development

No branches or pull requests

3 participants