Re: Error behaviour for max_input_vars

On Tue, Sep 13, 2022, 7:58 PM Mel Dafert <mel@dafert.at> wrote: > The options I see feasible are: > - A new ini setting max_input_vars_abort (default to 0), which, > if set > to 1, will abort the request if there are more input variables than > allowed. > - A method to reliably detect whether the input vars were truncated (eg. > function has_post_been_truncated(): bool), so the application > can > decide whether to abort or not. > - Deciding that max_input_vars is not relevant anymore and > should be > handled by the likes of Apache and NGINX, thus changing the default to > 0 and removing the setting > over a deprecation period. Creating more ini settings is not very exciting. I do really like option 2 though.