{"id":4599,"date":"2021-03-24T07:59:05","date_gmt":"2021-03-24T07:59:05","guid":{"rendered":"https:\/\/jchost.pl\/blog\/?p=4599"},"modified":"2025-09-10T08:37:47","modified_gmt":"2025-09-10T08:37:47","slug":"blad-413-request-entity-too-large","status":"publish","type":"post","link":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/","title":{"rendered":"B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107?"},"content":{"rendered":"\n
\n
\n
\n
\n \n
\n
\n

B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107?<\/h1> <\/div>\n<\/div>\n <\/div>\n <\/div>\n <\/div>\n
\n
\n
\n <\/div>\n
\n \n
\n
\n

\u00a0<\/p>\n

B\u0142\u0105d 413 – Request Entity Too Large\u00a0<\/h2>\n

Tworz\u0105c lub administruj\u0105c witryn\u0119 internetow\u0105 mo\u017cesz napotka\u0107 nieoczekiwane b\u0142\u0119dy HTTP<\/a>. Podczas gdy niekt\u00f3re z nich s\u0105 \u0142atwe do rozwi\u0105zania, inne wymagaj\u0105 po\u015bwi\u0119cenia wi\u0119kszej ilo\u015bci czasu. Przyk\u0142adem b\u0142\u0119du zaliczaj\u0105cego si\u0119 do tej pierwszej grupy jest HTTP 413 – Request Entity Too Large.<\/strong><\/p> <\/div>\n<\/div>\n\n

\n
\n \"blad \n <\/div>\n \n \n <\/div>\n\n
\n
\n

\u00a0<\/p>\n

Ten komunikat wyst\u0119puje, gdy pr\u00f3bujesz przes\u0142a\u0107 zbyt du\u017cy plik na serwer.<\/strong> Jest do\u015b\u0107 powszechny w\u015br\u00f3d u\u017cytkownik\u00f3w WordPress, kt\u00f3rzy korzystaj\u0105 z niedrogich plan\u00f3w hostingu wsp\u00f3\u0142dzielonego do hostowania swojej witryny.<\/p>\n

Dobr\u0105 wiadomo\u015bci\u0105 jest to, \u017ce je\u015bli napotkasz omawiany b\u0142\u0105d, mo\u017cesz go szybko i \u0142atwo rozwi\u0105za\u0107 poprzez zmian\u0119 konfiguracji serwera. Nie musisz by\u0107 w tym celu ekspertem technicznym.<\/p>\n

W tym przewodniku odpowiemy, co oznacza b\u0142\u0105d HTTP 413 (Request Entity Too Large) i poka\u017cemy 4 sposoby jak go naprawi\u0107 \u2013 zar\u00f3wno w witrynie WordPress, pliku PHP.ini jak i plikach konfiguracyjnych serwera Apache i Ngnix.<\/p> <\/div>\n<\/div>\n\n

\n
\n

\u00a0<\/p>\n

\u00a0<\/p>\n

Co oznacza b\u0142\u0105d 413 (Request Entity Too Large)?<\/h3>\n

HTTP 413 (Request Entity Too Large)<\/strong> jest komunikatem HTTP, kt\u00f3ry oznacza, \u017ce \u017c\u0105danie nie mo\u017ce zosta\u0107 przetworzone, poniewa\u017c rozmiar pliku wys\u0142anego przez klienta (np. przegl\u0105dark\u0119) przekracza limit rozmiaru ustanowionego przez serwer.<\/p> <\/div>\n<\/div>\n\n

\n
\n \"znaczenie \n <\/div>\n \n \n <\/div>\n\n
\n
\n

\u00a0<\/p>\n

Firmy hostingowe nak\u0142adaj\u0105 ograniczenia rozmiaru na przesy\u0142ane pliki, aby zapobiec przeci\u0105\u017ceniu serwera i przekroczeniu pojemno\u015bci przestrzeni dyskowej<\/strong> przez u\u017cytkownik\u00f3w.<\/p>\n

Chocia\u017c te limity s\u0105 ustalane dla Twojego w\u0142asnego dobra, cz\u0119sto mog\u0105 przeszkadza\u0107 w rozwoju Twojej witryny. Jest to szczeg\u00f3lnie uci\u0105\u017cliwe w przypadku stron opartych na systemie zarz\u0105dzania tre\u015bci\u0105<\/a>, takich jak WordPress, na kt\u00f3rych cz\u0119sto przesy\u0142asz du\u017ce pliki multimedialne oraz pliki motyw\u00f3w i wtyczek.<\/p> <\/div>\n<\/div>\n\n

\n
\n

Warto wiedzie\u0107:<\/strong> \u201eError 413 Request Entity Too Large\u201d w wolnym t\u0142umaczeniu oznacza zbyt du\u017c\u0105 jednostk\u0119 \u017c\u0105dania.<\/p>\n<\/div>\n <\/div>\n<\/div>\n\n\n

\n
\n

Sprawd\u017a najszybszy na rynku hosting WordPress<\/a> oraz hosting Ecommerce<\/a>.<\/p><\/div>\n <\/div>\n<\/div>\n\n\n

\n
\n

\u00a0<\/p>\n

\u00a0<\/p>\n

Jak naprawi\u0107 b\u0142\u0105d HTTP 413?<\/h3>\n

Domy\u015blny limit rozmiaru przesy\u0142ania zale\u017cy od konfiguracji serwera. Tak wi\u0119c, je\u015bli chcesz naprawi\u0107 b\u0142\u0105d 413 – Request Entity Too Large wystarczy, \u017ce zwi\u0119kszysz wspomniany limit lub \u2013 w przypadku plik\u00f3w multimedialnych – zmniejszysz wag\u0119 przesy\u0142anego pliku za pomoc\u0105 zewn\u0119trznych narz\u0119dzi.<\/p> <\/div>\n<\/div>\n\n

\n
\n

Notatka:<\/strong> Jednym ze sposob\u00f3w na ca\u0142kowite unikni\u0119cie omawianego b\u0142\u0119du jest skorzystanie z aplikacji FTP<\/a> (np. Filezilla) podczas przesy\u0142ania wi\u0119kszych plik\u00f3w.<\/p><\/div>\n <\/div>\n<\/div>\n\n\n

\n
\n

\u00a0<\/p>\n

Wi\u0119kszo\u015b\u0107 z poni\u017cszych metod wymaga minimalnych zmian w plikach serwerowych, dlatego te\u017c przed rozpocz\u0119ciem procesu naprawy, zalecamy wykonanie kopii zapasowej.<\/p>\n

Oto, jak naprawi\u0107 b\u0142\u0105d HTTP 413 w r\u00f3\u017cnych \u015brodowiskach internetowych:<\/strong><\/p>\n

\u00a0<\/p>\n

1. Dopasuj ustawienia PHP<\/strong><\/h4>\n

Naj\u0142atwiejsz\u0105 metod\u0105 zwi\u0119kszenia limitu przesy\u0142ania jest modyfikacja ustawie\u0144 PHP. Mo\u017cesz jej dokona\u0107 z poziomu panelu hostingowego, bez \u017cadnego kodowania, lub poprzez edycj\u0119 parametr\u00f3w w pliku PHP.ini.<\/p> <\/div>\n<\/div>\n\n

\n
\n \"ustawienia \n <\/div>\n \n \n <\/div>\n\n
\n
\n

\u00a0<\/p>\n

Je\u015bli jeste\u015b klientem JCHost.pl, w celu zmiany ustawie\u0144 PHP, zaloguj si\u0119 do panelu hostingowego, wybierz \u201eDodatkowe funkcje\u201d<\/strong>, kliknij \u201eSelect PHP version\u201d<\/strong>, a nast\u0119pnie przejd\u017a do zak\u0142adki \u201eOptions\u201d<\/strong>. W otwartym oknie dopasuj ustawienia \u2018max_execution_time\u2019<\/em> (np. 300), \u2018post_max_size\u2019<\/em> (np. 64M) oraz \u2018upload_max_filesize\u2019<\/em> (np. 64M).<\/p> <\/div>\n<\/div>\n\n

\n
\n

Warto wiedzie\u0107:<\/strong> Plik PHP.ini znajduje si\u0119 w katalogu \/etc\/php7\/fpm\/php.ini (nazwa folderu \u2018php7\u2019 r\u00f3\u017cni si\u0119 w zale\u017cno\u015bci od wersji PHP).<\/p><\/div>\n <\/div>\n<\/div>\n\n\n

\n
\n

\u00a0<\/p>\n

\u00a0<\/p>\n

2. Edytuj plik functions.php (strona WordPress)<\/strong><\/h4>\n

W przypadku stron WordPress, najpopularniejsz\u0105 opcj\u0105 rozwi\u0105zania problemu z komunikatem HTTP 413 jest modyfikacja pliku functions.php, kt\u00f3ry znajduje si\u0119 w folderze u\u017cywanego przez Ciebie motywu. Plik ten jest odpowiedzialny za definiowanie klas i akcji w witrynie WordPress.<\/p> <\/div>\n<\/div>\n\n

\n
\n \"wordpress \n <\/div>\n \n \n <\/div>\n\n
\n
\n

\u00a0<\/p>\n

Aby zmodyfikowa\u0107 ten plik, otw\u00f3rz katalog \/public_html\/<\/strong>, kliknij \/wp-content\/<\/strong> i przejd\u017a do \/themes\/<\/strong>. Nast\u0119pnie znajd\u017a folder motywu, z kt\u00f3rego aktualnie korzystasz, otw\u00f3rz plik functions.php<\/strong> i wprowad\u017a w nim nast\u0119puj\u0105cy kod:<\/p> <\/div>\n<\/div>\n\n

\n
\n 
@ini_set( \u2018upload_max_size\u2019 , \u201964M\u2019 );\n@ini_set( \u2018post_max_size\u2019, \u201964M\u2019);\n@ini_set( \u2018max_execution_time\u2019, \u2018300\u2019 );<\/span> <\/code><\/pre>\n    <\/div>\n<\/div>\n\n
\n        
\n        
\u00a0<\/p>\n
\u00a0<\/p>\n
3. Zmodyfikuj dyrektywy .htaccess (serwer Apache)<\/strong><\/h4>\n
Je\u015bli Twoja witryna internetowa jest hostowana na serwerze Apache, mo\u017cesz naprawi\u0107 b\u0142\u0105d 413 (Request Entity Too Large) za pomoc\u0105 modyfikacji dyrektyw w pliku .htaccess. Owe dyrektywy s\u0105 jednym z najwa\u017cniejszych element\u00f3w konfiguracyjnych.<\/p>    <\/div>\n<\/div>\n\n
\n        
\n            \"htaccess    \n        <\/div>\n    \n    \n        <\/div>\n\n
\n        
\n        
\u00a0<\/p>\n
W celu dopasowania dyrektyw odpowiedzialnych za limity przesy\u0142anych plik\u00f3w, przejd\u017a do katalogu \/public_html\/<\/strong> i otw\u00f3rz plik .htaccess<\/strong>. Nast\u0119pnie na samym ko\u0144cu dodaj poni\u017cszy kod:<\/p>    <\/div>\n<\/div>\n\n
\n        
\n        
php_value upload_max_filesize 64M\nphp_value post_max_size 64M\nphp_value max_execution_time 300<\/span> <\/code><\/pre>\n    <\/div>\n<\/div>\n\n
\n        
\n        
\u00a0<\/p>\n
\u00a0<\/p>\n
4. Zmodyfikuj dyrektywy nginx.conf (serwer Ngnix)<\/strong><\/h4>\n
Na stronach internetowych, kt\u00f3re s\u0105 hostowane na serwerze Ngnix, dyrektywa odpowiedzialna za maksymalny rozmiar \u017c\u0105dania to \u2018client_max_body_size<\/em>\u2019. Jest zdefiniowana w pliku konfiguracyjnym o nazwie ngnix.conf.<\/p>    <\/div>\n<\/div>\n\n
\n        
\n            \"ngnix.conf    \n        <\/div>\n    \n    \n        <\/div>\n\n
\n        
\n        
\u00a0<\/p>\n
Aby zwi\u0119kszy\u0107 limit przesy\u0142ania, otw\u00f3rz folder \/etc\/ngnix\/<\/strong> i rozpocznij edycj\u0119 pliku ngnix.conf<\/strong>. Nast\u0119pnie edytuj wspomnian\u0105 wy\u017cej dyrektyw\u0119, zmieniaj\u0105c warto\u015b\u0107 na \u201864M\u2019. Je\u015bli nie zosta\u0142a wcze\u015bniej dodana, umie\u015b\u0107 j\u0105 na ko\u0144cu bloku \u2018server\u2019, \u2018location\u2019 lub \u2018http\u2019, np.:<\/p>    <\/div>\n<\/div>\n\n
\n        
\n        
server {\n          ...\n          client_max_body_size 64M;\n}<\/span> <\/code><\/pre>\n    <\/div>\n<\/div>\n\n
\n        
\n            <\/div>\n<\/div>\n\n
\n    
\n                
Warto wiedzie\u0107:<\/strong> Je\u015bli \u017cadne z powy\u017cszych rozwi\u0105za\u0144 nie dzia\u0142a, problem mo\u017ce wynika\u0107 z dostawcy CDN<\/a>. W takim przypadku powiniene\u015b zapozna\u0107 si\u0119 z dokumentacj\u0105 us\u0142ugi lub skontaktowa\u0107 si\u0119 z pomoc\u0105 techniczn\u0105.<\/p><\/div>\n    <\/div>\n<\/div>\n\n\n
\n        
\n        
\u00a0<\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>\n
\u00a0<\/p>    <\/div>\n<\/div>\n\n
\n    
\n                
Odbieramy telefony, odpisujemy na maile, nie ukrywamy koszt\u00f3w, a dodatkowo oferujemy najszybsze pakiety hostingowe na rynku. Uwa\u017casz, \u017ce to zwroty marketingowe? Sprawd\u017a sam\/a!<\/p>\n
Je\u015bli nie b\u0119dziesz zadowolony\/a, zwr\u00f3cimy Ci pieni\u0105dze.
Twoje strony i sklepy przeniesiemy za darmo!<\/strong><\/p>\n
Hosting WordPress<\/a> – Hosting Magento<\/a><\/p><\/div>\n    <\/div>\n<\/div>\n\n\n
\n    
\n                
Je\u017celi masz jakiekolwiek pytania, skontaktuj si\u0119 z nami! Kliknij tutaj<\/a>.<\/p>\n
Chcesz dowiedzie\u0107 si\u0119 o nas troch\u0119 wi\u0119cej? Przejd\u017a na stron\u0119 JCHost.pl<\/a>.<\/p><\/div>\n    <\/div>\n<\/div>\n\n        <\/div>\n                    
\n                            <\/div>\n                        <\/div>\n        <\/div>\n        <\/div>\n","protected":false},"excerpt":{"rendered":"
B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107? \u00a0 B\u0142\u0105d 413 – Request Entity Too Large\u00a0 Tworz\u0105c lub administruj\u0105c witryn\u0119 internetow\u0105 mo\u017cesz napotka\u0107 nieoczekiwane b\u0142\u0119dy HTTP. Podczas gdy niekt\u00f3re z nich s\u0105 \u0142atwe do rozwi\u0105zania, inne wymagaj\u0105 po\u015bwi\u0119cenia wi\u0119kszej ilo\u015bci czasu. Przyk\u0142adem b\u0142\u0119du zaliczaj\u0105cego si\u0119 do tej pierwszej grupy jest HTTP […]<\/p>\n","protected":false},"author":1,"featured_media":4697,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1],"tags":[],"class_list":["post-4599","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-uncategorized","has-post-title","has-post-date","has-post-category","has-post-tag","has-post-comment","has-post-author",""],"yoast_head":"\nB\u0142\u0105d 413 (Request Entity Too Large) - co oznacza i jak naprawi\u0107? - JCHost.pl<\/title>\n<meta name=\"description\" content=\"Kod HTTP 413 - Request Entity Too Large wskazuje na przekroczenie limitu rozmiaru przesy\u0142ania. Zobacz, jak zwi\u0119kszy\u0107 ten limit!\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/\" \/>\n<meta property=\"og:locale\" content=\"pl_PL\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"413 (Request Entity Too Large) - jak naprawi\u0107?\" \/>\n<meta property=\"og:description\" content=\"Wejd\u017a na bloga, by pozna\u0107 4 rozwi\u0105zania \u2192\" \/>\n<meta property=\"og:url\" content=\"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog o hostingu i dla hostingu\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/jchostpl\/\" \/>\n<meta property=\"article:published_time\" content=\"2021-03-24T07:59:05+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-09-10T08:37:47+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2021\/04\/blad-413-request-entity-too-large.png\" \/>\n\t<meta property=\"og:image:width\" content=\"879\" \/>\n\t<meta property=\"og:image:height\" content=\"469\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Ekipa\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Napisane przez\" \/>\n\t<meta name=\"twitter:data1\" content=\"Ekipa\" \/>\n\t<meta name=\"twitter:label2\" content=\"Szacowany czas czytania\" \/>\n\t<meta name=\"twitter:data2\" content=\"5 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/\"},\"author\":{\"name\":\"Ekipa\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#\\\/schema\\\/person\\\/5c0718f08eb37ba283bce590a6a97475\"},\"headline\":\"B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107?\",\"datePublished\":\"2021-03-24T07:59:05+00:00\",\"dateModified\":\"2025-09-10T08:37:47+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/\"},\"wordCount\":915,\"commentCount\":0,\"publisher\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/blad-413-request-entity-too-large.png\",\"articleSection\":[\"Uncategorized\"],\"inLanguage\":\"pl-PL\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/\",\"url\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/\",\"name\":\"B\u0142\u0105d 413 (Request Entity Too Large) - co oznacza i jak naprawi\u0107? - JCHost.pl\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/blad-413-request-entity-too-large.png\",\"datePublished\":\"2021-03-24T07:59:05+00:00\",\"dateModified\":\"2025-09-10T08:37:47+00:00\",\"description\":\"Kod HTTP 413 - Request Entity Too Large wskazuje na przekroczenie limitu rozmiaru przesy\u0142ania. Zobacz, jak zwi\u0119kszy\u0107 ten limit!\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#breadcrumb\"},\"inLanguage\":\"pl-PL\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#primaryimage\",\"url\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/blad-413-request-entity-too-large.png\",\"contentUrl\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/wp-content\\\/uploads\\\/2021\\\/04\\\/blad-413-request-entity-too-large.png\",\"width\":879,\"height\":469,\"caption\":\"blad 413 (request entity too large)\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/blad-413-request-entity-too-large\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Strona g\u0142\u00f3wna\",\"item\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107?\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/\",\"name\":\"Blog o hostingu i dla hostingu\",\"description\":\"Blog hostingowy dla ka\u017cdego!\",\"publisher\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"pl-PL\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#organization\",\"name\":\"blog.jchost.pl\",\"url\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/11\\\/blog-hostingowy-logo-JCHost.jpg\",\"contentUrl\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/wp-content\\\/uploads\\\/2017\\\/11\\\/blog-hostingowy-logo-JCHost.jpg\",\"width\":229,\"height\":80,\"caption\":\"blog.jchost.pl\"},\"image\":{\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.facebook.com\\\/jchostpl\\\/\",\"https:\\\/\\\/www.youtube.com\\\/channel\\\/UC6myB18cMX1a5bAJ6WChQPw\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/#\\\/schema\\\/person\\\/5c0718f08eb37ba283bce590a6a97475\",\"name\":\"Ekipa\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"pl-PL\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6b555ed5d05df6e3eab514d0387177f840ba1c281811baacd9c8f74fb1a0661d?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6b555ed5d05df6e3eab514d0387177f840ba1c281811baacd9c8f74fb1a0661d?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/6b555ed5d05df6e3eab514d0387177f840ba1c281811baacd9c8f74fb1a0661d?s=96&d=mm&r=g\",\"caption\":\"Ekipa\"},\"url\":\"https:\\\/\\\/jchost.pl\\\/blog\\\/author\\\/admin\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO plugin. -->","yoast_head_json":{"title":"B\u0142\u0105d 413 (Request Entity Too Large) - co oznacza i jak naprawi\u0107? - JCHost.pl","description":"Kod HTTP 413 - Request Entity Too Large wskazuje na przekroczenie limitu rozmiaru przesy\u0142ania. Zobacz, jak zwi\u0119kszy\u0107 ten limit!","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/","og_locale":"pl_PL","og_type":"article","og_title":"413 (Request Entity Too Large) - jak naprawi\u0107?","og_description":"Wejd\u017a na bloga, by pozna\u0107 4 rozwi\u0105zania \u2192","og_url":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/","og_site_name":"Blog o hostingu i dla hostingu","article_publisher":"https:\/\/www.facebook.com\/jchostpl\/","article_published_time":"2021-03-24T07:59:05+00:00","article_modified_time":"2025-09-10T08:37:47+00:00","og_image":[{"width":879,"height":469,"url":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2021\/04\/blad-413-request-entity-too-large.png","type":"image\/png"}],"author":"Ekipa","twitter_card":"summary_large_image","twitter_misc":{"Napisane przez":"Ekipa","Szacowany czas czytania":"5 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#article","isPartOf":{"@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/"},"author":{"name":"Ekipa","@id":"https:\/\/jchost.pl\/blog\/#\/schema\/person\/5c0718f08eb37ba283bce590a6a97475"},"headline":"B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107?","datePublished":"2021-03-24T07:59:05+00:00","dateModified":"2025-09-10T08:37:47+00:00","mainEntityOfPage":{"@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/"},"wordCount":915,"commentCount":0,"publisher":{"@id":"https:\/\/jchost.pl\/blog\/#organization"},"image":{"@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#primaryimage"},"thumbnailUrl":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2021\/04\/blad-413-request-entity-too-large.png","articleSection":["Uncategorized"],"inLanguage":"pl-PL"},{"@type":"WebPage","@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/","url":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/","name":"B\u0142\u0105d 413 (Request Entity Too Large) - co oznacza i jak naprawi\u0107? - JCHost.pl","isPartOf":{"@id":"https:\/\/jchost.pl\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#primaryimage"},"image":{"@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#primaryimage"},"thumbnailUrl":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2021\/04\/blad-413-request-entity-too-large.png","datePublished":"2021-03-24T07:59:05+00:00","dateModified":"2025-09-10T08:37:47+00:00","description":"Kod HTTP 413 - Request Entity Too Large wskazuje na przekroczenie limitu rozmiaru przesy\u0142ania. Zobacz, jak zwi\u0119kszy\u0107 ten limit!","breadcrumb":{"@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#breadcrumb"},"inLanguage":"pl-PL","potentialAction":[{"@type":"ReadAction","target":["https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/"]}]},{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#primaryimage","url":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2021\/04\/blad-413-request-entity-too-large.png","contentUrl":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2021\/04\/blad-413-request-entity-too-large.png","width":879,"height":469,"caption":"blad 413 (request entity too large)"},{"@type":"BreadcrumbList","@id":"https:\/\/jchost.pl\/blog\/blad-413-request-entity-too-large\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Strona g\u0142\u00f3wna","item":"https:\/\/jchost.pl\/blog\/"},{"@type":"ListItem","position":2,"name":"B\u0142\u0105d 413 (Request Entity Too Large) – co oznacza i jak naprawi\u0107?"}]},{"@type":"WebSite","@id":"https:\/\/jchost.pl\/blog\/#website","url":"https:\/\/jchost.pl\/blog\/","name":"Blog o hostingu i dla hostingu","description":"Blog hostingowy dla ka\u017cdego!","publisher":{"@id":"https:\/\/jchost.pl\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/jchost.pl\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"pl-PL"},{"@type":"Organization","@id":"https:\/\/jchost.pl\/blog\/#organization","name":"blog.jchost.pl","url":"https:\/\/jchost.pl\/blog\/","logo":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/jchost.pl\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2017\/11\/blog-hostingowy-logo-JCHost.jpg","contentUrl":"https:\/\/jchost.pl\/blog\/wp-content\/uploads\/2017\/11\/blog-hostingowy-logo-JCHost.jpg","width":229,"height":80,"caption":"blog.jchost.pl"},"image":{"@id":"https:\/\/jchost.pl\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.facebook.com\/jchostpl\/","https:\/\/www.youtube.com\/channel\/UC6myB18cMX1a5bAJ6WChQPw"]},{"@type":"Person","@id":"https:\/\/jchost.pl\/blog\/#\/schema\/person\/5c0718f08eb37ba283bce590a6a97475","name":"Ekipa","image":{"@type":"ImageObject","inLanguage":"pl-PL","@id":"https:\/\/secure.gravatar.com\/avatar\/6b555ed5d05df6e3eab514d0387177f840ba1c281811baacd9c8f74fb1a0661d?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/6b555ed5d05df6e3eab514d0387177f840ba1c281811baacd9c8f74fb1a0661d?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/6b555ed5d05df6e3eab514d0387177f840ba1c281811baacd9c8f74fb1a0661d?s=96&d=mm&r=g","caption":"Ekipa"},"url":"https:\/\/jchost.pl\/blog\/author\/admin\/"}]}},"_links":{"self":[{"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/posts\/4599","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/comments?post=4599"}],"version-history":[{"count":25,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/posts\/4599\/revisions"}],"predecessor-version":[{"id":7866,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/posts\/4599\/revisions\/7866"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/media\/4697"}],"wp:attachment":[{"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/media?parent=4599"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/categories?post=4599"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/jchost.pl\/blog\/wp-json\/wp\/v2\/tags?post=4599"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}