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

Bug: Request entity too large #220

Closed
dlorenc opened this issue Mar 18, 2021 · 5 comments · Fixed by #264
Closed

Bug: Request entity too large #220

dlorenc opened this issue Mar 18, 2021 · 5 comments · Fixed by #264
Labels
enhancement New feature or request

Comments

@dlorenc
Copy link
Member

dlorenc commented Mar 18, 2021

I hit this when trying to upload a 3.7M artifact using the --artifact flag. It worked for me when passing in a URL. I think a reasonable limit makes sense here, but 3.7M seems like it should work. Not sure where to fix this.

@dlorenc
Copy link
Member Author

dlorenc commented Mar 18, 2021

Ooh, apparently we can use DEBUG=1 to trace these!

<center><h1>413 Request Entity Too Large</h1></center>
<hr><center>nginx</center>

so it's actually coming from our ingress.

@lukehinds lukehinds added the enhancement New feature or request label Mar 19, 2021
@asraa
Copy link
Contributor

asraa commented Apr 12, 2021

Looks like this is fixed with a max of 32 mb.

Do we want to catch the error earlier?

@dlorenc
Copy link
Member Author

dlorenc commented Apr 12, 2021

Ah good call, yeah we could keep this open to track erroring earlier in the client.

We can also bump this up higher if we want.

@bobcallaway
Copy link
Member

reopening per discussion at #264 (comment)

@bobcallaway
Copy link
Member

Rekor service now correctly formats this error message and is handled correctly by rekor-cli

[POST /api/v1/log/entries][413] createLogEntry default &{Code:413 Message:Request Entity Too Large}

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

Successfully merging a pull request may close this issue.

4 participants