Merge pull request #2175 from spacewander/gwts

ResponseHeaderModifier is already standard since the version now is 0.7+
kubernetes-sigs · Jul 10, 2023 · 0bdd240 · 0bdd240
2 parents 7cc35dd + 96469db
commit 0bdd240
Show file tree

Hide file tree

Showing 2 changed files with 1 addition and 7 deletions.
diff --git a/geps/gep-1323.md b/geps/gep-1323.md
@@ -1,7 +1,7 @@
 # GEP 1323: Response Header Filter
 
 * Issue: [#1323](https://github.com/kubernetes-sigs/gateway-api/issues/1323)
-* Status: Experimental
+* Status: Standard
 
 > **Note**: This GEP is exempt from the [Probationary Period][expprob] rules of
 > our GEP overview as it existed before those rules did, and so it has been

diff --git a/site-src/guides/http-header-modifier.md b/site-src/guides/http-header-modifier.md
@@ -43,12 +43,6 @@ Using the example above would remove the `x-request-id` header from the HTTP req
 
 ### HTTP Response Header Modifier
 
-!!! info "Experimental Channel"
-
-    The `ResponseHeaderModifier` filter described below is currently only included in the
-    "Experimental" channel of Gateway API. Starting in v0.7.0, this
-    feature will graduate to the "Standard" channel.
-
 Just like editing request headers can be useful, the same goes for response headers. For example, it allows teams to add/remove cookies for only a certain backend, which can help in identifying certain users that were redirected to that backend previously.
 
 Another potential use case could be when you have a frontend that needs to know whether it’s talking to a stable or a beta version of the backend server, in order to render different UI or adapt its response parsing accordingly.