You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi team—quick question. The JSS proxy currently fetches → renders → sends the response, which effectively owns the entire request pipeline and hides req/res from renderView. This makes it hard to add standard concerns (Server-Timing, ETag/304, custom headers, SWR, short-circuiting routes) and can introduce routing/version coupling.
Is there a plan to offer a more composable API (e.g., separate fetch + render utilities or a middleware that passes req/res through) so apps can manage headers, caching, and observability themselves?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Description
Hi team—quick question. The JSS proxy currently fetches → renders → sends the response, which effectively owns the entire request pipeline and hides req/res from renderView. This makes it hard to add standard concerns (Server-Timing, ETag/304, custom headers, SWR, short-circuiting routes) and can introduce routing/version coupling.
Is there a plan to offer a more composable API (e.g., separate fetch + render utilities or a middleware that passes req/res through) so apps can manage headers, caching, and observability themselves?
Additional information
No response
All reactions