Spec unclear for scheme redirects in HTTPRoute

[robscott]

What happened:
As feedback in #1908, @howardjohn pointed out that it's currently unclear how scheme and port interact in the redirect filter. Two examples below:

1. If an incoming request is to http://example.com (on port 80), and the redirect simply requests "HTTPS" scheme without specifying port, what should the implementation do?

A) https://example.com
B) https://example.com:80

2. Similarly if an incoming request is to http://example.com:80, and the redirect simply requests "HTTPS" scheme without specifying port, what should the implementation do?

A) https://example.com
B) https://example.com:80

3. Finally, if an incoming request is to http://example.com:8080, and the redirect simply requests "HTTPS" scheme without specifying port, what should the implementation do?

A) https://example.com
B) https://example.com:8080

What you expected to happen:
The spec should tell implementations how to treat these scenarios.

[shaneutt]

It would be nice if we could get this sorted out before GA, since HTTPRoute will be the first GA route.

Could use some help from a community member to bring this up in discussions, tease this out and then get a patch to the documentation.

/help

[k8s-ci-robot]

@shaneutt:
This request has been marked as needing help from a contributor.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• Does this issue have zero to low barrier of entry?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-help command.

In response to this:

It would be nice if we could get this sorted out before GA, since HTTPRoute will be the first GA route.

Could use some help from a community member to bring this up in discussions, tease this out and then get a patch to the documentation.

/help

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[gauravkghildiyal]

I've already been involved with this so lets take it all the way.

/assign

[gauravkghildiyal]

I've put my thoughts in this doc. Will try to bring this up in some Gateway API meeting -- if time permits :)