redirect with 307 does not work as expected about remix HOT 5 CLOSED

This is expected, when you do a redirect after a POST, the browser sends a new GET to the target location, so any response body sent by the POST is lost.

from remix.

@sergiodxa it seems 307 doesn't work correctly either. https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/307

I've updated accordingly

from remix.

You're losing the ?index query param when you do Location: url.pathname so the POST that is re-sent is trying to hit the root route action and there isn't one, so you're getting a 405. If you need to re-POSt to the same action you'll need to append ?index to your Location header (and then avoid redirect loops in some way 😉 ).

from remix.

@brophdawg11 @sergiodxa I guess what I'm wondering is how I could potentially achieve something like this as highlighted by @ryanflorence in roadmap 8. https://youtu.be/fHel4d-It5Q?list=PLXoynULbYuEDR_w8LJKRIkGheWpFfiMiR&t=757 while retaining the state of the submission if this is even a reasonable expectation?

from remix.

That video is mostly talking in hypotheticals - could you outline exactly the UX you're trying to achieve so we're on the same page? 303 redirects are not intended to preserve the submission body, while 307/308's are intended to preserve the submission body.

from remix.