Sulu Media Manager: per-MIME-type upload size constraint absent from admin UI

Sulu's Media Manager relies on a single upload_max_filesize directive from PHP configuration, currently defaulting to 2 MiB, without a mechanism to impose distinct limits based on MIME type. This design means that all file categories—images, videos, documents, archives—share the same ceiling, and the application only validates size after the complete payload has been received by the server. As a result, uploads exceeding the threshold consume network and disk resources before triggering a generic error, creating a potential bottleneck when multiple editors submit large assets concurrently. The admin UI provides no per‑type override, leaving administrators dependent on server‑level php.ini or .user.ini adjustments, which carry site‑wide implications and may conflict with other PHP applications hosted in the same environment.

• Can Sulu be configured to enforce independent size limits for image, video, and document MIME types without modifying global PHP settings?
• Does the current validation flow prevent premature rejection, and what are the performance trade‑offs under concurrent upload loads?
• What alternative mechanisms, such as web server‑level request size limits or Sulu‑specific bundles, can mitigate the identified bottleneck while preserving support for large legitimate assets?