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
Iirc in H3v1 the request body would be cached and so multiple requests to readBody would work. This allowed for middlewares to possibly manipulate the request if required before executing the actual route.
In H3v2, this feature is/was removed (or maybe Mandella got the better of me?).
Should we potentially cache the request? This technically wouldn't really go against web standards because readBody is a wrapper around req.body...
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
H3
Uh oh!
There was an error while loading. Please reload this page.
-
Iirc in H3v1 the request body would be cached and so multiple requests to
readBodywould work. This allowed for middlewares to possibly manipulate the request if required before executing the actual route.In H3v2, this feature is/was removed (or maybe Mandella got the better of me?).
Should we potentially cache the request? This technically wouldn't really go against web standards because
readBodyis a wrapper aroundreq.body...Beta Was this translation helpful? Give feedback.
All reactions