Merge pull request #1031 from DuendeSoftware/v8-updates

V8 docs updates

Author: wcabus

astro/src/content/docs/identityserver/tokens/fapi-2-0-specification.md

@@ -192,11 +192,9 @@ You are now FAPI 2.0 compliant and ready to secure your high-value assets with D
 
 ## HTTP 303 Redirects :badge[v8.0]
 
-FAPI 2.0 Section 5.3.2.2 requires that POST endpoints use HTTP 303 (See Other) redirects rather than HTTP 302. IdentityServer has supported this behavior via the `UseHttp303Redirects` option since v7.3.
+FAPI 2.0 Section 5.3.2.2 requires that POST endpoints use HTTP 303 (See Other) redirects rather than HTTP 302.
 
-:::note
-As of v8.0, IdentityServer unconditionally uses HTTP 303 (See Other) redirects from POST endpoints, in compliance with FAPI 2.0 Section 5.3.2.2. The `UseHttp303Redirects` option has been removed — this behavior is always active.
-:::
+As of v8.0, IdentityServer unconditionally uses HTTP 303 (See Other) redirects from POST endpoints, in compliance with FAPI 2.0 Section 5.3.2.2.
 
 ## Conformance Report :badge[v8.0]
 

astro/src/content/docs/identityserver/upgrades/v7_4-to-v8_0.md

@@ -238,12 +238,8 @@ dependency. Use the `CancellationToken` passed directly to interface methods ins
 
 ### HTTP 303 Redirects Now Unconditional
 
-`UserInteractionOptions.UseHttp303Redirects` has been removed. IdentityServer now always uses
-HTTP 303 (See Other) for redirects from POST endpoints, in compliance with
-[FAPI 2.0 Section 5.3.2.2](https://openid.net/specs/fapi-2_0-security-profile.html).
-
-No action is needed unless you explicitly set `UseHttp303Redirects = false` in a previous version.
-If so, remove that setting — the redirect behavior can no longer be changed.
+IdentityServer now always uses HTTP 303 (See Other) for redirects from POST endpoints,
+in compliance with [FAPI 2.0 Section 5.3.2.2](https://openid.net/specs/fapi-2_0-security-profile.html).
 
 ### IClientStore.GetAllClientsAsync Now Required