HttpClient's HttpParser offers no default or optional
limits on header sizes or the number of headers in an
HTTP response. As a result, challenging large input can
cause the HttpParser to use an unbounded amount of
memory, causing an OutOfMemoryError.
Some discussion of this issue is in HttpClient's old
Bugzilla system at:
http://issues.apache.org/bugzilla/show_bug.cgi?id=25468
And I've filed a new issue with HttpClient's new JIRA
system at:
http://issues.apache.org/jira/browse/HTTPCLIENT-566
However, we will likely have to work around this in our
own code -- the HttpClient committers tend write off
these kinds of shortcomings as not the library's concern.
--
An URL which triggered an HttpParser-related OOME on
recent .IT crawls was:
http://peeper.axisinc.com/nph-update3.cgi
(It appears to be a faulty implementation of a
mime-multipart replace server-push functionality.)
Karl Thiessen
None
1.10.0
Public
|
Date: 2007-03-14 01:07
|
|
Date: 2006-06-09 01:22 Logged In: YES |
| Field | Old Value | Date | By |
|---|---|---|---|
| summary | Contain HttpClient HttpParser's OutOfMemoryError risk | 2006-09-11 22:03 | karl-ia |
| status_id | Open | 2006-09-11 22:03 | karl-ia |
| close_date | - | 2006-09-11 22:03 | karl-ia |
| assigned_to | gojomo | 2006-06-09 01:22 | gojomo |
| resolution_id | None | 2006-06-09 01:22 | gojomo |
| artifact_group_id | None | 2006-06-01 23:27 | gojomo |
| assigned_to | nobody | 2006-06-01 23:27 | gojomo |