Rudder

It seems to actually been a jetty.xml problem, see: http://datatables.net/forums/discussion/comment/15037

http://stackoverflow.com/questions/11914555/jetty-http-413-header-full-error-java-scala

So perhaps it only a developper-environment error ?

François ARMAND wrote:

So perhaps it only a developper-environment error ?

Could well be. I've been manipulating all the screens in 2.9.1 over the past few days, pretty intensively, and clicking on all sorts of buttons, and never saw this error.

This is the (for non-enlightened people) workaround from irc:

"the correction should be easy (basically, adding <Set name="requestHeaderSize">8192</Set> in /opt/rudder/jetty7/etc/jetty.xml)"

The good place to add the line seems to be in https://github.com/Normation/rudder-packages/blob/master/rudder-jetty/SOURCES/Makefile#L47, along with
"# Change jetty's default settings to listen on localhost only"

One info:

I can trigger this most easily if i have change requests enabled.
No idea how I could inspect "my" cookie at time of the error, but it seems to grow.

You can use the liveHTTP header extension to extract your cookie if you are using firefox.

Applied in changeset packages:commit:b6eac47f84fb75ebc0d649debf643e60ef117839.

Ok, this did not fix the issue, one user reported the same issue. Increasing the size of the requestHeaderSize did not improve the result, only clearing cookies did solve the issue

This was corrected with #6160 in Rudder 2.10.10 and 2.11.7 (and 3.0 and up).