Project

General

Profile

Bug #4378

White page with HTTP status: 413: FULL head

Added by François ARMAND about 6 years ago. Updated about 5 years ago.

Status:
Released
Priority:
1
Category:
Web - UI & UX
Target version:
Severity:
User visibility:
Effort required:
Priority:

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

Related to Rudder - Bug #6146: Rudder stores too much or too big cookies, causing white page with HTTP status: 413: FULL headReleased2015-01-20Actions

Associated revisions

Revision ff4d72d9 (diff)
Added by Benoît PECCATTE over 5 years ago

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

Revision b6eac47f
Added by Jonathan CLARKE over 5 years ago

Merge pull request #499 from peckpeck/bug_4378/white_page_with_http_status_413_full_head

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

History

#1

Updated by François ARMAND about 6 years ago

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 ?

#2

Updated by Vincent MEMBRÉ about 6 years ago

  • Target version changed from 2.9.2 to 2.9.3
#3

Updated by Jonathan CLARKE about 6 years ago

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.

#4

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.9.3 to 2.9.4
#5

Updated by Vincent MEMBRÉ almost 6 years ago

  • Target version changed from 2.9.4 to 2.9.5
#6

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.9.5 to 2.9.6
#7

Updated by Jonathan CLARKE over 5 years ago

  • Target version changed from 2.9.6 to 2.9.7
#8

Updated by Jonathan CLARKE over 5 years ago

  • Target version changed from 2.9.7 to 150
#9

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 150 to 2.10.4
#10

Updated by Nicolas PERRON over 5 years ago

  • Target version changed from 2.10.4 to 2.10.5
#11

Updated by Vincent MEMBRÉ over 5 years ago

  • Target version changed from 2.10.5 to 2.10.6
#12

Updated by François ARMAND over 5 years ago

  • Priority changed from 2 to 1

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

The solution seems to increase Jetty buffer size.

#13

Updated by Florian Heigl over 5 years ago

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

#14

Updated by François ARMAND over 5 years ago

  • Description updated (diff)

Updating the description to highlight the possible workarounds

#15

Updated by François ARMAND over 5 years ago

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"

#16

Updated by François ARMAND over 5 years ago

  • 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 ?

#17

Updated by Matthieu CERDA over 5 years ago

  • Target version changed from 2.10.6 to 2.10.7
#18

Updated by Benoît PECCATTE over 5 years ago

  • 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
#19

Updated by Benoît PECCATTE over 5 years ago

  • Target version changed from 2.10.7 to 2.6.19
#20

Updated by Jonathan CLARKE over 5 years ago

  • Assignee changed from Jonathan CLARKE to Benoît PECCATTE
#21

Updated by Florian Heigl over 5 years ago

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.

#22

Updated by Benoît PECCATTE over 5 years ago

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

#23

Updated by Benoît PECCATTE over 5 years ago

  • 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
#24

Updated by Benoît PECCATTE over 5 years ago

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

Applied in changeset packages:commit:ff4d72d952f54423bf64d078c812bb58fe541885.

#25

Updated by Jonathan CLARKE over 5 years ago

Applied in changeset packages:commit:b6eac47f84fb75ebc0d649debf643e60ef117839.

#26

Updated by Vincent MEMBRÉ over 5 years ago

  • 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.

#27

Updated by Nicolas CHARLES about 5 years ago

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

#28

Updated by François ARMAND about 5 years ago

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

Also available in: Atom PDF