RavenVue / Vue plugins: 413 Request Entity Too Large
See original GitHub issueI’m just getting started with Sentry/Raven. I’d like to get this running in Vue 2, but I’m experiencing an issue that might be a bug, or at least requires better documentation.
Environment
Vue 2, Webpack 2, raven-js
via yarn (npm). Attempting to use RavenVue
and Vue
plugins with .addPlugin(RavenVue, Vue)
.
What is the current behavior?
When using RavenVue
and Vue
plugins, I get a 413 (Request Entity Too Large)
error response. If I delete data.extra.propsData
in the config’s dataCallback
, the request will go through. What is the size limit, 100k (#339)?
Issue Analytics
- State:
- Created 6 years ago
- Comments:15 (3 by maintainers)
Top Results From Across the Web
Fix the "413 Request Entity Too Large" Error in WordPress
Request Entity Too Large occurs when you upload a file that's larger than the limit. Read this article to know how you can...
Read more >Error: 413 Request Entity Too Large using Vue storefront
When i am send the image more than (100kb) in post request it gave me the error of 413 status code This is...
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 >How to Fix the 413 Request Entity Too large ... - WPBeginner
This error usually occurs when you are trying to upload a theme or plugin file in WordPress. In this article, we will show...
Read more >How to Fix “413 Request Entity Too Large” Error in Node.js
I recently had to deal with the “413 Request Entity Too Large” Express error. After some research, I found out that this is...
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
@bjunc for now I settled with removing the fields unconditionally but this seems like a good approach as well. I wish Sentry provided an add-on to allow going over the limit.
@bjunc
https://github.com/getsentry/sentry-docs/pull/310
tl;dr
200kB, or 64kB you use
keepalive:true
in fetchno, it’s not JS SDK limitation, but rather a whole system’s
old SDK:
dataCallback
new SDK:beforeSend
or event processors once we document them fully100k, then send the whole thing. If not, go through and prune See my implementation of this approach here: https://github.com/getsentry/sentry-javascript/issues/874#issuecomment-379731186 which can be easily modified to be used in the Vue. We’ll most likely provide more straightforward solution moving forward.