HTTP Redirects (documentation issue)

[WarpRat]

There's a minor issue with the HTTP redirect documentation. This page has the following warning:

Note: 301 (default) and 302 are the only supported statusCodes.

However looking at the CRDs, it appears that there are more options supported now. At least as of 1.7.0:

> k explain httproute.spec.rules.filters.requestRedirect.statusCode
GROUP:      gateway.networking.k8s.io
KIND:       HTTPRoute
VERSION:    v1

FIELD: statusCode <integer>
ENUM:
    301
    302
    303
    307
    308

DESCRIPTION:
    StatusCode is the HTTP status code to be used in response.

    Note that values may be added to this enum, implementations
    must ensure that unknown values will not cause a crash.

    Unknown values here must result in the implementation setting the
    Accepted Condition for the Route to `status: False`, with a
    Reason of `UnsupportedValue`.

    Support: Core

[zirain]

This's a known issue from upstream(Gateway API v1.4) should be fixed in EG v1.7.1(Gateway API v1.4.1).

BTW, 303 307 and 308 will be supported in EG v1.8

[Aditya7880900936]

Hi @maintainers,

I would like to work on updating the HTTP redirect documentation
to clarify that currently only 301 and 302 are supported and that
support for 303/307/308 is planned for v1.8.

Please let me know if this approach sounds good.

[Aditya7880900936]

Hi @zirain @WarpRat , I have opened a documentation update PR to clarify the currently
supported redirect status codes and mention planned future support.