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

"Request Line is too large" error #359

Closed
tkuhn opened this issue Aug 26, 2021 · 4 comments
Closed

"Request Line is too large" error #359

tkuhn opened this issue Aug 26, 2021 · 4 comments
Assignees

Comments

@tkuhn
Copy link

tkuhn commented Aug 26, 2021

I am trying to set up a plain grlc service (via Docker) and I am now getting the error "Request Line is too large". See here: http://grlcplain.nanopubs.lod.labs.vu.nl/api-git/peta-pico/fpsi-queries/get-superpattern-reviews

Any idea what's going on here?

@c-martinez c-martinez self-assigned this Sep 1, 2021
@c-martinez
Copy link
Collaborator

Strange one -- it seems to work fine on a different grlc instance:

http://grlc.io/api-git/peta-pico/fpsi-queries/get-superpattern-reviews

I assume you have an nginx proxy somewhere? Perhaps try increasing the client_max_body_size in your nginx.conf

@tkuhn
Copy link
Author

tkuhn commented Oct 18, 2021

No, increasing client_max_body_size doesn't help.

The error message looks like it comes from something called Gunicorn: https://serverfault.com/questions/564464/nginx-request-line-too-large

And grlc is using Gunicorn, it seems? There is a solution in the link above, but I have no idea how I can pass such an argument to the Gunicorn part of grlc...

@tkuhn
Copy link
Author

tkuhn commented Oct 19, 2021

I figured this one out, and it was entirely on my side. I started to get similar messages from other services of my university as well, and it seems one of these applications stored huge cookies, which was then sent to all applications running under vu.nl, and this was starting to hit some limits. Clearing the cookies for vu.nl solved the problem.

Sorry for bothering you with this issue, which wasn't on your side at all.

@c-martinez
Copy link
Collaborator

Ah, good to know, thanks @tkuhn! Glad you managed to solve the issue :-)

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

2 participants