{"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\">Codul de eroare HTTP 413 \"Con\u021binut prea mare\" \u00eenseamn\u0103 c\u0103 un server sau o alt\u0103 component\u0103 a c\u0103ii de solicitare a respins o solicitare deoarece dimensiunea acesteia a dep\u0103\u0219it limita permis\u0103. Solicitarea poate con\u021bine un fi\u0219ier \u00eenc\u0103rcat, date dintr-un formular, o tem\u0103, un plugin, o copie de rezerv\u0103 sau un alt con\u021binut voluminos. Limita poate fi impus\u0103 de serverul web, de PHP, de un proxy invers, de un CDN sau de CMS-ul care prime\u0219te solicitarea.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Un r\u0103spuns 413 nu \u00eenseamn\u0103 \u00eentotdeauna c\u0103 fi\u0219ierul \u00een sine este deteriorat. De obicei, \u00eenseamn\u0103 c\u0103 solicitarea a fost respins\u0103 \u00eenainte ca urm\u0103torul strat de procesare s\u0103 o poat\u0103 accepta. Prima sarcin\u0103 este identificarea stratului care a returnat r\u0103spunsul. Solu\u021bia corect\u0103 depinde de acel strat.<\/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\">Cuprins<\/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\">Ce \u00eenseamn\u0103 codul de eroare HTTP 413?<\/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\/#Unde_poate_fi_respingere_solicitarea\">Unde poate fi respins\u0103 solicitarea?<\/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\">Cum se identific\u0103 stratul limitant<\/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\">Cum s\u0103 regla\u021bi limita \u00een siguran\u021b\u0103<\/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\">Cum se valideaz\u0103 modificarea<\/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\">Cum s\u0103 preveni\u021bi cererile prea mari<\/a><\/li><\/ul><\/nav><\/div>\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Ce_\u00eenseamn\u0103_HTTP_413\"><\/span>Ce \u00eenseamn\u0103 HTTP 413?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<\/div>\n\n<div id=\"mybox-2683950335\" 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\">O cerere HTTP con\u021bine un corp atunci c\u00e2nd trimite date c\u0103tre un server. O cerere de \u00eenc\u0103rcare include, de obicei, fi\u0219ierul \u0219i datele aferente din formular \u00een acest corp. Un r\u0103spuns 413 \u00eenseamn\u0103 c\u0103 \u00eentregul corp al cererii, sau o parte a acestuia care intr\u0103 sub inciden\u021ba unei reguli de dimensiune, dep\u0103\u0219e\u0219te limita permis\u0103 de stratul de recep\u021bie.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Se pot aplica mai multe limite la o singur\u0103 \u00eenc\u0103rcare. Un server web poate respinge cererea \u00een etapa de conectare sau de procesare a cererii. PHP poate aplica o limit\u0103 \u00een timp ce preg\u0103te\u0219te datele pentru o aplica\u021bie. Un proxy invers sau un CDN poate respinge cererea \u00eenainte ca aceasta s\u0103 ajung\u0103 la serverul de origine. Un CMS poate, de asemenea, s\u0103 aplice propria sa regul\u0103 de \u00eenc\u0103rcare sau de cerere. Cea mai mic\u0103 limit\u0103 aplicabil\u0103 determin\u0103 dac\u0103 cererea are succes.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"Where_can_the_request_be_rejected\"><\/span>Unde poate fi respins\u0103 solicitarea?<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Strat<\/th><th>Ce controleaz\u0103<\/th><th>Ce sugereaz\u0103 o respingere<\/th><\/tr><\/thead><tbody><tr><td>Server web<\/td><td>Solicitarea primit\u0103 de server<\/td><td>Solicitarea poate fi respins\u0103 \u00eenainte ca aplica\u021bia s\u0103 se execute<\/td><\/tr><tr><td>PHP<\/td><td>Datele transmise scripturilor PHP<\/td><td>Limita de procesare PHP poate fi mai mic\u0103 dec\u00e2t dimensiunea fi\u0219ierului<\/td><\/tr><tr><td>Proxy invers sau CDN<\/td><td>Solicit\u0103rile care trec printr-un intermediar<\/td><td>Intermediarul poate respinge solicitarea \u00eenainte ca aceasta s\u0103 ajung\u0103 \u00een mediul de g\u0103zduire<\/td><\/tr><tr><td>CMS<\/td><td>\u00cenc\u0103rc\u0103rile gestionate \u00een interiorul aplica\u021biei<\/td><td>Aplica\u021bia poate afi\u0219a propria limit\u0103 de \u00eenc\u0103rcare chiar \u0219i atunci c\u00e2nd straturile inferioare permit cererea<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n<p class=\"wp-block-paragraph\">WordPress limiteaz\u0103 dimensiunea maxim\u0103 a fi\u0219ierelor \u00eenc\u0103rcate prin panoul s\u0103u de administrare. \u00cen func\u021bie de configura\u021bia site-ului web, aceast\u0103 limit\u0103 poate afecta fi\u0219ierele media mai mari, temele, pluginurile \u0219i copiile de rezerv\u0103. Limita poate fi m\u0103rit\u0103 prin modificarea configura\u021biei site-ului web, inclusiv a fi\u0219ierului <code>.htaccess<\/code>, acolo unde aceast\u0103 metod\u0103 este aplicabil\u0103. Consulta\u021bi <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-se-mareste-dimensiunea-maxima-a-fisierelor-incarcate-in-wordpress\/\">instruc\u021biunile mybox pentru m\u0103rirea dimensiunii maxime de \u00eenc\u0103rcare \u00een WordPress<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_identify_the_limiting_layer\"><\/span>Cum se identific\u0103 stratul limitativ<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li><strong>\u00cenregistra\u021bi locul \u00een care apare eroarea.<\/strong> Re\u021bine\u021bi dac\u0103 codul 413 este afi\u0219at de browser, de o pagin\u0103 proxy sau CDN, de serverul web sau de panoul de administrare al CMS-ului. R\u0103spunsul vizibil poate indica care strat a procesat solicitarea.<\/li>\n\n\n\n<li><strong>Verifica\u021bi tipul cererii.<\/strong> Confirma\u021bi dac\u0103 eroarea apare \u00een timpul \u00eenc\u0103rc\u0103rii unui fi\u0219ier, a trimiterii unui formular, a unui import, a \u00eenc\u0103rc\u0103rii unei copii de rezerv\u0103 sau a unei alte ac\u021biuni care trimite date c\u0103tre server.<\/li>\n\n\n\n<li><strong>Compara\u021bi cu o solicitare mai mic\u0103.<\/strong> Trimite\u021bi un fi\u0219ier sau o \u00eenc\u0103rc\u0103tur\u0103 util\u0103 mai mic\u0103 folosind aceea\u0219i ac\u021biune. Dac\u0103 solicitarea mai mic\u0103 are succes, iar cea mai mare returneaz\u0103 codul 413, e\u0219ecul este cauzat de o limit\u0103 de dimensiune a solicit\u0103rii.<\/li>\n\n\n\n<li><strong>Verifica\u021bi fiecare limit\u0103 \u00een ordinea cererii.<\/strong> Examina\u021bi set\u0103rile serverului web, PHP, proxy-ului invers sau CDN-ului \u0219i ale CMS-ului care se aplic\u0103 cererii. O modificare la un strat nu poate anula o limit\u0103 inferioar\u0103 la un alt strat.<\/li>\n\n\n\n<li><strong>Analiza\u021bi sursa r\u0103spunsului.<\/strong> O pagin\u0103 de r\u0103spuns, un jurnal de server, un jurnal de proxy sau un mesaj al aplica\u021biei poate indica componenta care a respins solicitarea. Utiliza\u021bi componenta men\u021bionat\u0103 acolo ca punct de plecare pentru modificare.<\/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>Cum s\u0103 ajusta\u021bi limita \u00een siguran\u021b\u0103<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<p class=\"wp-block-paragraph\">Modifica\u021bi limita la nivelul stratului care a respins solicitarea. M\u0103ri\u021bi doar valoarea relevant\u0103 \u0219i seta\u021bi-o la un nivel suficient de ridicat pentru fi\u0219ierul sau solicitarea vizat\u0103, \u00een loc s\u0103 m\u0103ri\u021bi c\u00e2t mai mult posibil fiecare solicitare. Dac\u0103 mai multe straturi au o limit\u0103, valoarea necesar\u0103 trebuie s\u0103 fie permis\u0103 de toate straturile implicate.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">Efectua\u021bi c\u00e2te o modificare de configurare pe r\u00e2nd. P\u0103stra\u021bi o eviden\u021b\u0103 a valorii anterioare, astfel \u00eenc\u00e2t aceasta s\u0103 poat\u0103 fi restabilit\u0103 dac\u0103 rezultatul nu este cel a\u0219teptat. Aplica\u021bi modificarea folosind metoda de configurare disponibil\u0103 pentru acel strat. Pentru \u00eenc\u0103rc\u0103rile \u00een WordPress, utiliza\u021bi metoda de configurare a site-ului web aplicabil\u0103, descris\u0103 \u00een articolul <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/cum-se-mareste-dimensiunea-maxima-a-fisierelor-incarcate-in-wordpress\/\">mybox despre dimensiunea \u00eenc\u0103rc\u0103rilor \u00een WordPress<\/a>.<\/p>\n\n\n\n<p class=\"wp-block-paragraph\">O limit\u0103 mai mare cre\u0219te cantitatea de date pe care serverul \u0219i aplica\u021bia ar putea fi nevoite s\u0103 o primeasc\u0103 \u0219i s\u0103 o proceseze. Prin urmare, aceasta poate cre\u0219te timpul de procesare \u0219i consumul de resurse. Limita ar trebui s\u0103 corespund\u0103 unei cerin\u021be reale, cum ar fi un fi\u0219ier de backup sau un fi\u0219ier media cunoscut, \u0219i nu ar trebui m\u0103rit\u0103 f\u0103r\u0103 o necesitate clar\u0103.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_validate_the_change\"><\/span>Cum se valideaz\u0103 modificarea<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ol class=\"wp-block-list\">\n<li>Re\u00eencerca\u021bi aceea\u0219i \u00eenc\u0103rcare sau cerere care a returnat codul de eroare 413.<\/li>\n\n\n\n<li>Testa\u021bi cu un fi\u0219ier sub noua limit\u0103 prev\u0103zut\u0103.<\/li>\n\n\n\n<li>Testa\u021bi cu un fi\u0219ier aproape de limit\u0103 pentru a confirma c\u0103 limita se comport\u0103 conform a\u0219tept\u0103rilor.<\/li>\n\n\n\n<li>Confirma\u021bi c\u0103 CMS-ul finalizeaz\u0103 opera\u021biunea \u0219i c\u0103 elementul \u00eenc\u0103rcat este disponibil ulterior.<\/li>\n\n\n\n<li>Verifica\u021bi dac\u0103 un alt strat returneaz\u0103 \u00een continuare codul 413. Dac\u0103 da, continua\u021bi cu acel strat \u00een loc s\u0103 modifica\u021bi \u00een mod repetat setarea CMS-ului.<\/li>\n<\/ol>\n\n\n\n<p class=\"wp-block-paragraph\">Un test reu\u0219it ar trebui s\u0103 arate c\u0103 solicitarea ajunge la aplica\u021bia vizat\u0103 \u0219i se finalizeaz\u0103 \u00een mod normal. Dac\u0103 codul de eroare se schimb\u0103 de la 413 la 503, este posibil ca limita de dimensiune s\u0103 nu mai fie cauza imediat\u0103 a bloc\u0103rii, ci mediul de g\u0103zduire s\u0103 nu poat\u0103 procesa solicitarea deoarece resursele disponibile ale pachetului de g\u0103zduire au fost dep\u0103\u0219ite. Un cod 503 indic\u0103 o problem\u0103 temporar\u0103 legat\u0103 de resurse sau de performan\u021b\u0103, nu este acela\u0219i r\u0103spuns ca 413. Consulta\u021bi <a href=\"https:\/\/mybox.com\/help\/ro\/baza-de-cunostinte\/eroare-503-resursele-disponibile-ale-pachetului-de-gazduire-au-fost-utilizate\/\">informa\u021biile mybox despre eroarea 503<\/a>.<\/p>\n\n\n\n<h2 class=\"wp-block-heading\"><span class=\"ez-toc-section\" id=\"How_to_prevent_oversized_requests\"><\/span>Cum se pot preveni solicit\u0103rile supradimensionate<span class=\"ez-toc-section-end\"><\/span><\/h2>\n\n\n\n<ul class=\"wp-block-list\">\n<li>Seta\u021bi limita \u00een func\u021bie de cel mai mare fi\u0219ier sau de cea mai mare solicitare de care site-ul web are nevoie efectiv.<\/li>\n\n\n\n<li>Men\u021bine\u021bi limite separate, aliniate \u00eentre serverul web, PHP, proxy-ul invers sau CDN \u0219i CMS.<\/li>\n\n\n\n<li>Utiliza\u021bi fi\u0219iere mai mici sau \u00eemp\u0103r\u021bi\u021bi opera\u021biunile mari atunci c\u00e2nd aplica\u021bia accept\u0103 acest flux de lucru.<\/li>\n\n\n\n<li>Verifica\u021bi fi\u0219ierele media, temele, pluginurile \u0219i copiile de rezerv\u0103 de dimensiuni mari \u00eenainte de a le \u00eenc\u0103rca prin CMS.<\/li>\n\n\n\n<li>Monitoriza\u021bi solicit\u0103rile mari repetate, deoarece acestea pot consuma capacitatea de procesare.<\/li>\n<\/ul>\n\n\n\n<p class=\"wp-block-paragraph\">Codul de eroare HTTP 413 indic\u0103 o problem\u0103 legat\u0103 de dimensiunea solicit\u0103rii. Identifica\u021bi stratul care a respins solicitarea, ajusta\u021bi acel strat \u0219i orice limit\u0103 inferioar\u0103 care se aplic\u0103 \u00een continuare, apoi valida\u021bi printr-o \u00eenc\u0103rcare controlat\u0103. Men\u021bine\u021bi limita corelat\u0103 cu un caz de utilizare real, astfel \u00eenc\u00e2t solicit\u0103rile mai mari s\u0103 nu creeze probleme de performan\u021b\u0103 sau expuneri de securitate care pot fi evitate.<\/p>\n<\/div>","protected":false},"author":1,"featured_media":0,"parent":0,"menu_order":0,"template":"","format":"standard","manualknowledgebasecat":[25,11396,11526,11496,51,11490],"manual_kb_tag":[11900,11901,11902,11903,11904,11905,11906,11907,11908,11909],"class_list":["post-13499","manual_kb","type-manual_kb","status-publish","format-standard","hentry","manualknowledgebasecat-hosting","manualknowledgebasecat-website-performance","manualknowledgebasecat-apis-http-web-protocols","manualknowledgebasecat-debugging-testing-deployment","manualknowledgebasecat-types-of-http-errors","manualknowledgebasecat-developer-resources","manual_kb_tag-41-content-too-large","manual_kb_tag-http-41-error","manual_kb_tag-content-too-large-error","manual_kb_tag-request-size-limit","manual_kb_tag-file-upload-limit","manual_kb_tag-upload-size-limit","manual_kb_tag-max-upload-size","manual_kb_tag-web-server-limits","manual_kb_tag-reverse-proxy-limits","manual_kb_tag-application-upload-limit"],"_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}]}}