Bug 22733 - gnu.java.net.protocol.http.Connection doesn't handle null from DataInputStream.readLine()
Summary: gnu.java.net.protocol.http.Connection doesn't handle null from DataInputStrea...
Status: RESOLVED FIXED
Alias: None
Product: classpath
Classification: Unclassified
Component: classpath (show other bugs)
Version: unspecified
: P3 normal
Target Milestone: ---
Assignee: Not yet assigned to anyone
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2004-04-12 00:03 UTC by from-classpath
Modified: 2005-07-23 22:54 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:
Known to work:
Known to fail:
Last reconfirmed:

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 from-classpath 2004-04-12 00:03:48 UTC 
Like the summary says.

Though it was a bug with my HTTP sender which returned a malformed HTTP response, Connection doesn't check the return value of inputStream.readLine() in receiveReply() before using indexOf on it.

The current version of Connection in  CVS (1.16) has this problem.

Mark Baker -- distobj@acm.org
Comment 1 from-classpath 2004-05-07 11:31:32 UTC 
And what does JDK did in you case ? Throw an IOException ? or an EOFException ? Can you provide a testcase we can use for regression tests ?
Comment 2 from-classpath 2004-12-01 12:54:12 UTC 
This bug got obsoleted by the HTTP protocol implementation from GNU inetlib. This implementation does not use DataInputStream.readLine() at all. The merged version is commited th CVS and will be in GNU classpath 0.13.