This is the mail archive of the
java-prs@sourceware.cygnus.com
mailing list for the Java project.
Re: java.net/170: HTTP client code treats headers as body
- To: warrenl at cygnus dot com
- Subject: Re: java.net/170: HTTP client code treats headers as body
- From: John Stracke <francis at ecal dot com>
- Date: 10 Mar 2000 02:50:00 -0000
- Cc: java-prs at sourceware dot cygnus dot com,
- Reply-To: John Stracke <francis at ecal dot com>
The following reply was made to PR java.net/170; it has been noted by GNATS.
From: John Stracke <francis@ecal.com>
To: Bryce McKinlay <bryce@albatross.co.nz>
Cc: java-gnats@sourceware.cygnus.com
Subject: Re: java.net/170: HTTP client code treats headers as body
Date: Thu, 09 Mar 2000 21:45:58 -0500
Bryce McKinlay wrote:
> Actually, the second part of the 170 patch is wrong, I think. The http status
> line is what is returned by getHeaderField(0), so it shouldn't be skipped.
But it's not a header. Hmm...ah, here we are: the status line is accessible
through methods of java.net.HttpURLConnection: getResponseCode() and
getResponseMessage()...though there's no method to get the protocol version.
gcj doesn't currently implement getResponseCode() or getResponseMessage(). I'll
write them tonight or tomorrow.
--
/===============================================================\
|John Stracke | http://www.ecal.com |My opinions are my own. |
|Chief Scientist |==============================================|
|eCal Corp. |"This [OLE] isn't an API, this is a shaggy dog|
|francis@ecal.com|story in C!" -- Unknown |
\===============================================================/