Project

General

Profile

Actions

Bug #4378

closed

White page with HTTP status: 413: FULL head

Bug #4378: White page with HTTP status: 413: FULL head

Added by François ARMAND almost 12 years ago. Updated almost 11 years ago.

Status:
Released
Priority:
1 (highest)
Assignee:
Jonathan CLARKE
Category:
Web - UI & UX
Target version:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:

Description

When navigating on Rudder, sometimes I get a return status code of 413 (Full head).

That seems linked with the the addition of Datatable preference storage between pages.

And actually, if I removed some entries in the "cookie" panel of firebug, Rudder start to display things again.

So:
- browser-side workaround (temporary): clean cookies related to Rudder
- jetty-side workaround: add <Set name="requestHeaderSize">8192</Set> in /opt/rudder/jetty7/etc/jetty.xml, in the section about "Set connectors", as described in http://stackoverflow.com/questions/11914555/jetty-http-413-header-full-error-java-scala/11948304#11948304


Related issues 1 (0 open1 closed)

Related to Rudder - Bug #6146: Rudder stores too much or too big cookies, causing white page with HTTP status: 413: FULL headReleasedFrançois ARMANDActions

Updated by François ARMAND almost 12 years ago Actions #1

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 ?

Updated by Vincent MEMBRÉ almost 12 years ago Actions #2

  • Target version changed from 2.9.2 to 2.9.3

Updated by Jonathan CLARKE almost 12 years ago Actions #3

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.

Updated by Vincent MEMBRÉ almost 12 years ago Actions #4

  • Target version changed from 2.9.3 to 2.9.4

Updated by Vincent MEMBRÉ over 11 years ago Actions #5

  • Target version changed from 2.9.4 to 2.9.5

Updated by Vincent MEMBRÉ over 11 years ago Actions #6

  • Target version changed from 2.9.5 to 2.9.6

Updated by Jonathan CLARKE over 11 years ago Actions #7

  • Target version changed from 2.9.6 to 2.9.7

Updated by Jonathan CLARKE over 11 years ago Actions #8

  • Target version changed from 2.9.7 to 150

Updated by Vincent MEMBRÉ over 11 years ago Actions #9

  • Target version changed from 150 to 2.10.4

Updated by Nicolas PERRON over 11 years ago Actions #10

  • Target version changed from 2.10.4 to 2.10.5

Updated by Vincent MEMBRÉ over 11 years ago Actions #11

  • Target version changed from 2.10.5 to 2.10.6

Updated by François ARMAND about 11 years ago Actions #12

  • Priority changed from 2 to 1 (highest)

It seems that Florian hit that bug in a non-dev environment.

The solution seems to increase Jetty buffer size.

Updated by Florian Heigl about 11 years ago Actions #13

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)"

Updated by François ARMAND about 11 years ago Actions #14

  • Description updated (diff)

Updating the description to highlight the possible workarounds

Updated by François ARMAND about 11 years ago Actions #15

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"

Updated by François ARMAND about 11 years ago Actions #16

  • Assignee changed from François ARMAND to Benoît PECCATTE

My sed-foo is not sufficient for that, Benoit could you take a look at that ?

Updated by Matthieu CERDA about 11 years ago Actions #17

  • Target version changed from 2.10.6 to 2.10.7

Updated by Benoît PECCATTE about 11 years ago Actions #18

  • Status changed from 8 to Pending technical review
  • Assignee changed from Benoît PECCATTE to Jonathan CLARKE
  • Pull Request set to https://github.com/Normation/rudder-packages/pull/492

Updated by Benoît PECCATTE about 11 years ago Actions #19

  • Target version changed from 2.10.7 to 2.6.19

Updated by Jonathan CLARKE about 11 years ago Actions #20

  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE

Updated by Florian Heigl about 11 years ago Actions #21

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.

Updated by Benoît PECCATTE about 11 years ago Actions #22

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

Updated by Benoît PECCATTE about 11 years ago Actions #23

  • Assignee changed from Benoît PECCATTE to Jonathan CLARKE
  • Pull Request changed from https://github.com/Normation/rudder-packages/pull/492 to https://github.com/Normation/rudder-packages/pull/499

Updated by Benoît PECCATTE about 11 years ago Actions #24

  • Status changed from Pending technical review to Pending release
  • % Done changed from 0 to 100

Applied in changeset packages:commit:ff4d72d952f54423bf64d078c812bb58fe541885.

Updated by Jonathan CLARKE about 11 years ago Actions #25

Applied in changeset packages:commit:b6eac47f84fb75ebc0d649debf643e60ef117839.

Updated by Vincent MEMBRÉ about 11 years ago Actions #26

  • Status changed from Pending release to Released

This bug has been fixed in Rudder 2.6.19, 2.10.7 and 2.11.4, which were these days.

Updated by Nicolas CHARLES almost 11 years ago Actions #27

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

Updated by François ARMAND almost 11 years ago Actions #28

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

Actions

Also available in: PDF Atom