Allow setting the request method for Turbo Frame requests to avoid 414 Long URL errors #1284
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.
Currently the request that a Turbo Frame makes to load a page is hardcoded to a GET request. We came across an edge case where HTTP 414s were being thrown due to a very large request URL, in a complex form that heavily uses frames with URLs to hold form state.
The general approach to handling 414s is to switch to a POST. This PR adds the ability to declaratively do that on the frame element:
You need to provide:
method
="post"
params
= Something thatURLSearchParams
can interpret: stringified JSON, or form params.This will make a POST to
/my/url
, with the providedparams
in the POST body.