Follow-up to #2230121: Remove exit() from FormBuilder → and 📌 Allow both AJAX and non-AJAX forms to POST to dedicated URLs Postponed .
Drupal currently supports throwing an exception to exit the code flow and force an immediate redirect. This was implemented largely as a stop gap to allow the removal of direct response rendering and exits from core API's allowing better leverage of Symfony's HTTP stack.
Those API's should be refactored to allow common exit flows or redirecting without throwing an exception and then the Exception and its handling can hopefully be deprecated and retired.
N/A
Postponed
11.0 🔥
Last updated
It affects performance. It is often combined with the Needs profiling tag.
Worse Than Failure. Approximates the unpleasant remark made by Drupal developers when they first encounter a particular (mis)feature.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
📌 Make POST requests render cacheable Needs work is making POST requests render cacheable without changing form discovery, which doesn't affect this issue except it might mean it's worth looking at whether this issue is possible without doing 📌 Allow both AJAX and non-AJAX forms to POST to dedicated URLs Postponed .