Updating list of applicable projects and hitting maxHttpHeaderSize error
Description
When attempting to add an additional project to our list of applicable projects, we ran into a HTTP 400 error.
On doing some investigation, the problem was tracked down to the fact that the URL being attempted was sufficiently long as to be hitting the Tomcat maxHttpHeaderSize (defaults to 8192).
It seems like appending "&applicableProjects=12345" or similar, for each project, makes this prone to this kind of error, as once you get to sufficiently many projects, further additions will fail.
I didn't find anything in docs about this, so figured it might be worth raising this with you.
Is/was this a known issue?
Environment
Activity
Hi Russell,
No body complained about this because, I think no body needed that much of exception in the project list. I will check this.
Thanks for investigating! If in your research you arrive at a similar conclusion to what we did, is this the right place to ask for a feature request? Off the top off my head, not having this be a giant GET might be one way around it. Another approach might be to have an option to have the list be a list of exclusions instead of a list of inclusions.
Our situation is that the majority of projects do want to use reminders, however there are a handful that don’t. As such we are prevented from enabling globally, and have a very large list of included projects.
