Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

408 on large request upload #18543

Closed
Simerca opened this issue Oct 23, 2023 · 2 comments · Fixed by #18591
Closed

408 on large request upload #18543

Simerca opened this issue Oct 23, 2023 · 2 comments · Fixed by #18591
Labels
issue: bug Issue reporting a bug severity: medium If it breaks the basic use of the product but can be worked around source: core:strapi Source is core/strapi package status: confirmed Confirmed by a Strapi Team member or multiple community members

Comments

@Simerca
Copy link

Simerca commented Oct 23, 2023

Bug report

Describe the bug

When uploading a file that takes longer than 5 minutes to process in production with Node.js version 18, a client-side error 408 occurs. This is due to the default timeouts of Node.js version 18.

Steps to reproduce the behavior

  1. Use Node.js version 18 in production.
  2. Attempt to upload a file that takes more than 5 minutes to process.
  3. Observe the client-side error 408.

Expected behavior

I expect that timeouts can be configured or customized in Strapi, as the new default values in Node.js version 18 can result in error 408 for long operations such as file uploads.

https://fek.io/blog/what-is-new-in-node-js-18/

Additional context

I couldn't find information in the Strapi documentation about the possibility of configuring these timeouts via configuration variables.

I can fix it with downgrade to node 16

@derrickmehaffy
Copy link
Member

@innerdvations I thought you had a fix for this in DTS but I can't find the PR or if it was merged but I know we were planning on adding our own config option to configure the timeout.

@derrickmehaffy derrickmehaffy added issue: bug Issue reporting a bug severity: medium If it breaks the basic use of the product but can be worked around status: confirmed Confirmed by a Strapi Team member or multiple community members source: core:strapi Source is core/strapi package labels Oct 24, 2023
@innerdvations
Copy link
Contributor

Yeah, it's the default timeouts that were added in Node 18. This can be solved pretty easily by adding a config option. I'll see if I can do that this week.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Issue reporting a bug severity: medium If it breaks the basic use of the product but can be worked around source: core:strapi Source is core/strapi package status: confirmed Confirmed by a Strapi Team member or multiple community members
Projects
Status: Fixed/Shipped
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants