Repository navigation
Update the BFF docs based on the latest BFF Releases - #1250
Merged
Merged
Conversation
Starting with Duende.BFF 2.2.1, 2.3.1, 3.0.1, 3.1.1, 4.0.4, 4.1.3, 4.2.1, and 4.3.1, the YARP integration removes the inbound Cookie header on all routes by default. Document the new BffOptions.RemoveCookieHeaderFromYarpRequests option, the global opt-out, per-route control with YARP transforms, and the transform-ordering caveat. * options.md: add RemoveCookieHeaderFromYarpRequests to the API options * yarp.md: add "Cookie Header Removal" section (opt-out, per-route, ordering) * remote.mdx: note that the direct forwarder never forwards Cookie * troubleshooting.mdx: add entry for APIs that no longer receive cookies * upgrading/index.mdx: add "Behavior Changes In Patch Releases" section TODO (release day, once GHSA-vvg7-p7jw-8qr3 is published): add an advisory link to * upgrading/index.mdx, "YARP Routes No Longer Forward The Cookie Header" * fundamentals/apis/yarp.md, the "Changed in ..." note under "Cookie Header Removal"
Starting with Duende.BFF 4.0.4, 4.1.3, 4.2.1, and 4.3.1, remote APIs defined on a frontend (WithRemoteApis or Frontends:<name>:RemoteApis in configuration) require the anti-forgery header. Requests without it get 401 and a warning is logged. The check respects BffOptions.DisableAntiForgeryCheck and has no per-API opt-out. * multi-frontend/index.mdx: add "Anti-forgery Protection For Remote APIs" * multi-frontend/configuration.md: note the header requirement on remoteApis * getting-started/multi-frontend.mdx: note the header next to WithRemoteApis * options.md: DisableAntiForgeryCheck now covers frontend remote APIs * remote.mdx: point to the frontend remote API anti-forgery section * troubleshooting.mdx: mention frontend remote APIs under anti-forgery failures * upgrading/index.mdx: add the behavior change to the patch release section TODO (release day, once GHSA-4j63-5v5f-xcc4 is published): add an advisory link to * upgrading/index.mdx, "Frontend Remote APIs Require The Anti-Forgery Header" * fundamentals/multi-frontend/index.mdx, the "Changed in ..." note under "Anti-forgery Protection For Remote APIs"
Erwinvandervalk
requested review from
khalidabuhakmeh and
maartenba
and removed request for
maartenba
October 7, 2026 14:00
Erwinvandervalk
marked this pull request as ready for review
October 7, 2026 14:01
maartenba
requested changes
Oct 7, 2026
maartenba
left a comment
Member
There was a problem hiding this comment.
Couple of small suggestions
Co-authored-by: Maarten Balliauw <maarten.balliauw@duendesoftware.com>
Co-authored-by: Maarten Balliauw <maarten.balliauw@duendesoftware.com>
Member
|
Approved, feel free to merge @Erwinvandervalk |
maartenba
approved these changes
Oct 7, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Bumps the documentation to the latest versions of BFF.