Use custom headers to render RSC / remote components

[lazarv]

Description

The rendering logic is using the standard Accept HTTP header to drive the response type and caching used by the framework. This is not ideal for proxies and caching. See some additional information at #49

Suggested solution

Use custom HTTP headers to drive the rendering logic and to choose the response type and framework level caching type.

• use React-Server-RSC header to request an RSC payload response
• use React-Server-Remote header to request an RSC delegation response
• use React-Server-Standalone header to request standalone type routing logic

Existence of the above HTTP headers will drive the rendering logic.

Possible combinations are:

• React-Server-RSC with an optional React-Server-Standalone
• React-Server-Remote with an optional React-Server-Standalone

React-Server-RSC and React-Server-Remote can't be used in the same request!

Alternative

No response

Additional context

No response

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[lazarv]

This is now superseded by using a URL pattern instead of HTTP headers to select the response type.

[github-actions]

This issue has been locked since it has been closed for more than 30 days.

If you have found a concrete bug or regression related to it, please open a new bug report with a reproduction against the latest version of @lazarv/react-server. If you have any other comments you should create a new discussion.