🐛 BUG: wrangler publish - 413 Request Entity Too Large
See original GitHub issueWhat version of Wrangler
are you using?
2.0.8
What operating system are you using?
Windows
Describe the Bug
I upgraded my Workers Sites project from Wrangler v1 to v2(.0.8). I replaced my .toml file with an all command line implementation:
wrangler publish "workers-site\index.js" --name="dev-site" --compatibility-date="2022-06-05" --routes="www.dev-site.dev/*" --routes="dev-site.dev/*" --site="dist" --minify
Wrangler starts up and starts reading/uploading many files without issue. Then it hangs at a particular file every time, and a 413 Request Entity Too Large HTTP error is encountered:
That version\index.html file is only 32 bytes.
This site uploaded without issue using Wranger v1. It is only after upgrading to v2 that this problem has started occurring.
Issue Analytics
- State:
- Created a year ago
- Comments:9 (5 by maintainers)
Top Results From Across the Web
BUG: 413 Request Entity Too Large · Issue #1367 - GitHub
I found the reason for the bug. When wrangler builds, the build file name is newly created, so the bundle size continues to...
Read more >How to Solve the "413 Request Entity Too Large" Error - Kinsta
In this post, we'll take a look at how to solve the “413 Request Entity Too Large” error. We'll also give you a...
Read more >Fixing 413 Request Entity Too Large Errors - KeyCDN Support
A 413 Request Entity Too Large error occurs when a request made from a client is too large to be processed by the...
Read more >The Handmade.Network Feedback Megathread!
The server gives me the following error message: "413 Request Entity Too Large" - Animated GIFs are usually larger than 2.5MB.
Read more >getting an error while publish the on cloudflare workers?
As the error says, you need to run wrangler login or wrangler config to set the credentials for your account.
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
You’ve specified multiple routes correctly, that is indeed the right way to do it. And minify isn’t the default (yet), so you’re good.
I’m working on configuration / flags docs soon, and I’ll make it a point to specify this.
I’m surprised too!! I’ll verify it during the week.