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

occasional "413 Payload Too Large" #514

Open
macrozone opened this issue Jul 17, 2024 · 3 comments
Open

occasional "413 Payload Too Large" #514

macrozone opened this issue Jul 17, 2024 · 3 comments

Comments

@macrozone
Copy link

Describe the bug

Sometimes locally or on the ci/cd, there is a warning "413 Payload Too Large":

WARNING failed to contact remote cache: Error making HTTP request: HTTP status client error (413 Payload Too Large) for url (https://example.com/turbo/api/v8/artifacts/xxxxx?teamId=xxxx)

This will prevent some builds from beeing cached.

To Reproduce

the turbo cache is hosted on cloud-run, which has unlimited request size, unless http-1 is used (no limit on http2). I assume the client and cache are using http2.

So not sure where the limit is set. Typically its somewhere set on the body-parsers.

Expected behavior

No warning is shown, all artifacts are cached regardless of size

@macrozone
Copy link
Author

i currently assume the problem is with turbo repo not using http2 on the client

@macrozone
Copy link
Author

ok i have a solution, its not turbo, its when you host it on cloud run.

i managed to add native http2 support to this repo here. I will update my findings with an MR

@macrozone
Copy link
Author

macrozone commented Jul 17, 2024

opened a merge request #515

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant