{"id":13499,"date":"2026-09-07T09:19:08","date_gmt":"2026-09-07T07:19:08","guid":{"rendered":"https:\/\/mybox.com\/help\/?post_type=manual_kb&#038;p=13499"},"modified":"2026-09-07T09:19:12","modified_gmt":"2026-09-07T07:19:12","slug":"413-continut-prea-mare-explicatii-privind-limitele-de-incarcare-dimensiunile-cererilor-si-solutii-sigure","status":"publish","type":"manual_kb","link":"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/","title":{"rendered":"413 \u201eCon\u021binut prea mare\u201d \u2013 explica\u021bii: limite de \u00eenc\u0103rcare, dimensiuni ale cererilor \u0219i solu\u021bii sigure"},"content":{"rendered":"<div class=\"translation-block translation-block-merged\">\n<p class=\"wp-block-paragraph\">HTTP 413 Content Too Large means that a server or another part of the request path refused a request because its size exceeded an allowed limit. The request may contain a file upload, form data, a theme, a plugin, a backup, or another large payload. The limit can be enforced by the web server, PHP, a reverse proxy, a CDN, or the CMS that receives the request.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A 413 response does not always mean that the file itself is damaged. It usually means that the request was rejected before the next processing layer could accept it. The first task is to identify which layer returned the response. The correct fix depends on that layer.<\/p>\n\n\n\n<div id=\"ez-toc-container\" class=\"ez-toc-v2_0_86 ez-toc-wrap-left counter-hierarchy ez-toc-counter ez-toc-custom ez-toc-container-direction\">\n<div class=\"ez-toc-title-container\">\n<p class=\"ez-toc-title\" style=\"cursor:inherit\">Table of Contents<\/p>\n<span class=\"ez-toc-title-toggle\"><\/span><\/div>\n<nav><ul class='ez-toc-list ez-toc-list-level-1' ><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-1\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/#What_does_HTTP_413_mean\" >What does HTTP 413 mean?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-2\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/#Where_can_the_request_be_rejected\" >Where can the request be rejected?<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-3\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/#How_to_identify_the_limiting_layer\" >How to identify the limiting layer<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-4\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/#How_to_adjust_the_limit_safely\" >How to adjust the limit safely<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-5\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/#How_to_validate_the_change\" >How to validate the change<\/a><\/li><li class='ez-toc-page-1 ez-toc-heading-level-2'><a class=\"ez-toc-link ez-toc-heading-6\" href=\"https:\/\/mybox.com\/help\/ro\/knowledgebase\/413-content-too-large-explained-upload-limits-request-sizes-and-safe-fixes\/#How_to_prevent_oversized_requests\" >How to prevent oversized requests<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"What_does_HTTP_413_mean\"><\/span>What does HTTP 413 mean?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<\/div>\n\n<div id=\"mybox-3289980557\" class=\"mybox-content mybox-entity-placement\"><div class=\"early-access-banner-inpost\">\r\n  <div class=\"banner-left-inpost\">\r\n    <div class=\"icon-box-inpost\">\r\n      <img decoding=\"async\" src=\"https:\/\/mybox.com\/help\/wp-content\/uploads\/2026\/02\/square-info-icon.svg\" alt=\"Info\">\r\n    <\/div>\r\n    <div class=\"text-box-inpost\">\r\n      <span class=\"label-inpost\"><span class=\"translation-block translation-block-banner-text\">Acces timpuriu<\/span><\/span>\r\n      <h4><span class=\"translation-block translation-block-banner-text\">Mai ave\u021bi nevoie de ajutor?<\/span><\/h4>\r\n      <p><span class=\"translation-block translation-block-banner-text\">Contacta\u021bi echipa noastr\u0103 de servicii pentru clien\u021bi.<\/span><\/p>\r\n    <\/div>\r\n  <\/div>\r\n\r\n  <div class=\"banner-right-inpost\">\r\n    <a href=\"https:\/\/panel.mybox.com\/helpdesk2\/v\/list\/\" class=\"banner-button-inpost\"><span class=\"translation-block translation-block-banner-text\">Trimite mesaj<\/span><\/a>\r\n  <\/div>\r\n<\/div><\/div>\n\n<div class=\"translation-block translation-block-merged\"><p class=\"wp-block-paragraph\">An HTTP request contains a body when it sends data to a server. An upload request normally includes the file and related form data in this body. A 413 response means that the complete request body, or a part of it covered by a size rule, is larger than the receiving layer allows.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Several limits may apply to one upload. A web server can reject the request at the connection or request-processing stage. PHP can apply a limit while preparing data for an application. A reverse proxy or CDN can reject the request before it reaches the origin server. A CMS can also apply its own upload or request rule. The smallest applicable limit determines whether the request succeeds.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Where_can_the_request_be_rejected\"><\/span>Where can the request be rejected?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Layer<\/th><th>What it controls<\/th><th>What a rejection suggests<\/th><\/tr><\/thead><tbody><tr><td>Web server<\/td><td>The request received by the server<\/td><td>The request may be rejected before the application runs<\/td><\/tr><tr><td>PHP<\/td><td>Data passed to PHP scripts<\/td><td>The PHP processing limit may be lower than the file size<\/td><\/tr><tr><td>Reverse proxy or CDN<\/td><td>Requests passing through an intermediary<\/td><td>The intermediary may reject the request before it reaches the hosting environment<\/td><\/tr><tr><td>CMS<\/td><td>Uploads handled inside the application<\/td><td>The application may show its own upload limit even when lower layers allow the request<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress limits the maximum size of files uploaded through its administration panel. Depending on the website configuration, that limit can affect larger media files, themes, plugins, and backups. The limit can be increased by changing the website configuration, including the <code>.htaccess<\/code> file where that method applies. See <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-se-mareste-dimensiunea-maxima-a-fisierelor-incarcate-in-wordpress\/\">mybox instructions for increasing the maximum WordPress upload size<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_identify_the_limiting_layer\"><\/span>How to identify the limiting layer<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>Record where the error appears.<\/strong> Note whether 413 is shown by the browser, a proxy or CDN page, the web server, or the CMS administration panel. The visible response can indicate which layer handled the request.<\/li>\n\n\n\n<li><strong>Check the request type.<\/strong> Confirm whether the failure occurs during a file upload, a form submission, an import, a backup upload, or another action that sends data to the server.<\/li>\n\n\n\n<li><strong>Compare a smaller request.<\/strong> Send a smaller file or payload using the same action. If the smaller request succeeds and the larger one returns 413, the failure is consistent with a request-size limit.<\/li>\n\n\n\n<li><strong>Check each limit in request order.<\/strong> Review the web server, PHP, reverse proxy or CDN, and CMS settings that apply to the request. A change at one layer cannot override a lower limit at another layer.<\/li>\n\n\n\n<li><strong>Look at the response source.<\/strong> A response page, server log, proxy log, or application message may show which component rejected the request. Use the component named there as the starting point for the change.<\/li>\n<\/ol>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_adjust_the_limit_safely\"><\/span>How to adjust the limit safely<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Change the limit at the layer that rejected the request. Raise only the relevant value and set it high enough for the intended file or request, rather than making every request as large as possible. If more than one layer has a limit, the required value must be allowed by all layers involved.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Make one configuration change at a time. Keep a record of the previous value so it can be restored if the result is not as expected. Apply the change using the configuration method available for that layer. For WordPress uploads, use the applicable website configuration method described in the <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-se-mareste-dimensiunea-maxima-a-fisierelor-incarcate-in-wordpress\/\">mybox WordPress upload-size article<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">A larger limit increases the amount of data that the server and application may need to receive and process. It can therefore increase processing time and resource use. The limit should match a real requirement, such as a known backup or media file, and should not be raised without a clear need.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_validate_the_change\"><\/span>How to validate the change<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Retry the same upload or request that returned 413.<\/li>\n\n\n\n<li>Test with a file below the new intended limit.<\/li>\n\n\n\n<li>Test with a file near the limit to confirm that the boundary behaves as expected.<\/li>\n\n\n\n<li>Confirm that the CMS completes the operation and that the uploaded item is available afterward.<\/li>\n\n\n\n<li>Check whether another layer still returns 413. If it does, continue with that layer instead of repeatedly changing the CMS setting.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">A successful test should show that the request reaches the intended application and completes normally. If the request changes from 413 to 503, the size limit may no longer be the immediate blocker, but the hosting environment may be unable to process the request because the available resources of the hosting package have been exceeded. A 503 is a temporary resource or performance issue, not the same response as 413. See <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/eroare-503-resursele-disponibile-ale-pachetului-de-gazduire-au-fost-utilizate\/\">mybox information about error 503<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_prevent_oversized_requests\"><\/span>How to prevent oversized requests<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Set the limit around the largest file or request that the website actually needs.<\/li>\n\n\n\n<li>Keep separate limits aligned across the web server, PHP, reverse proxy or CDN, and CMS.<\/li>\n\n\n\n<li>Use smaller files or split large operations when the application supports that workflow.<\/li>\n\n\n\n<li>Review large media, themes, plugins, and backups before uploading them through the CMS.<\/li>\n\n\n\n<li>Monitor repeated large requests because they can consume processing capacity.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">HTTP 413 identifies a request-size problem. Find the layer that rejected the request, adjust that layer and any lower limit that still applies, then validate with a controlled upload. Keep the limit tied to a real use case so larger requests do not create avoidable performance or security exposure.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[43],"manual_kb_tag":[],"class_list":["post-13499","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-website-errors"],"_links":{"self":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13499","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb"}],"about":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/types\/manual_kb"}],"author":[{"embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/users\/1"}],"version-history":[{"count":1,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13499\/revisions"}],"predecessor-version":[{"id":13500,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb\/13499\/revisions\/13500"}],"wp:attachment":[{"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/media?parent=13499"}],"wp:term":[{"taxonomy":"manualknowledgebasecat","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manualknowledgebasecat?post=13499"},{"taxonomy":"manual_kb_tag","embeddable":true,"href":"https:\/\/mybox.com\/help\/ro\/wp-json\/wp\/v2\/manual_kb_tag?post=13499"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}