How to pass option to set raw-body limit? about next-auth HOT 11 CLOSED

Thanks for the issue.

Doh! Is this a default limit on the body of POST submissions? (Is it is low as that? Ouch.)

That should be no problem to fix. If you have any copy/paste bits of the relevant config, link to docs or a rough example of how to set it so that that we can expose it as an option that would be most helpful to save me looking up / adding the wrong thing as I seem to vaguely recall there are at least a couple of options that related to max POST size.

from next-auth.

Hi @iaincollins. Just created a simple PR that solves this. It's tried and tested. I hope you can merge soon 👍

from next-auth.

Hi @iaincollins. Do you have time to have a look at my PR that solves this? Do you need help/contributors on this project? I'll be happy to assist.

from next-auth.

Thanks for following up @jenssogaard! I only saw it because you did - I'm getting so many notifications from GitHub these days I am not noticing some of them 😬

That was great thanks, I'll push it out in a release this weekend (or sooner if I can).

from next-auth.

If you would really like it from tomorrow I can push it out as a beta in NPM then make it a full release at the weekend (so will only need to switch version briefly). If it's urgent before next week just let me know and I'll do that (I should rig that up automatically really…)

from next-auth.

@iaincollins it's not urgent. But I wouldn't mind a push to NPM soon 😄

from next-auth.

@iaincollins can you release the minor update soon?

from next-auth.

Thank you for the update and sorry there ended up being no more updates to 1.x in NPM - I was super busy for a while and didn't have the time.

Hopefully this won't be an issue in the upcoming release of 2.0, which doesn't rely on Express, so I think it's safe to close this off now.

from next-auth.

Hey!

Sorry for reopening such an old issue, I am trying to allow users top change their profile image and sending a base64 of the image and I think it reaches this issue.

The person logs in no problem in the backend but the session is never set probably because it hits this

from next-auth.

hi @SaraVieira, I suggest you open a new issue with a reproduction if you have some problems

from next-auth.

Hey!

That makes sense, it's hard to reproduce in a small project.

Will try to do it today, if I don't ignore it because it's not that important

from next-auth.