The textarea for configuring Shell or Batch scripts ToolInstallers is linked to a check method:
When the script is modified, it gets URL-encoded and sent as parameter of a GET query, which easily fails if the script is a bit verbose (Jenkins gives an error 414 if the URL is >8KB for instance, but the error may be different if using proxy servers).
I see the Pipeline editor textarea uses POST request instead:
The linked PR is simply about doing the same for the AbstractCommandInstaller.command textarea.
Note that an alternative would be to get rid of the "doCheckCommand" method, whose only purpose is to check the script is not empty...