Bug 46552 – Could there be a logging for requests exceeding maxHttpHeaderSize

Bug 46552 - Could there be a logging for requests exceeding maxHttpHeaderSize


Summary:	Could there be a logging for requests exceeding maxHttpHeaderSize

Status:	RESOLVED FIXED

Product:	Tomcat 5
Classification:	Unclassified
Component:	Connector:HTTP
Version:	Unknown
Hardware:	PC Windows Vista

Importance:	P2 normal (vote)
Target Milestone:	---
Assigned To:	Tomcat Developers Mailing List

URL:
Keywords:

Depends on:
Blocks:
	Show dependency tree

Reported:	2009-01-16 14:56 UTC by Benjamin Papez
Modified:	2009-06-13 13:31 UTC (History)
CC List:	0 users

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Benjamin Papez 2009-01-16 14:56:06 UTC

We recently had a case, where a customer was reporting Internal Server errors and it was quite hard to find the reason, until we realized that the problem was the maxHttpHeaderSize limit, which caused Tomcat to simply send back an Internal Server error.

Would it be possible to at least indicate in the log that a request has been rejected ?

Comment 1 Mark Thomas 2009-04-09 04:01:42 UTC

This is essentially the same as bug 46125. I have proposed a backport of the same fix for 5.5.x. This will:
- ensure a 400 response is issued rather than the current 200
- log a message (at debug level)
- removes an odd error message

http://people.apache.org/~markt/patches/2009-04-09-bug46552.patch

Comment 2 Mark Thomas 2009-06-13 13:31:44 UTC

This has been fixed in 5.5.x and will be included in 5.5.28 onwards.