This is the mail archive of the
gcc-bugs@gcc.gnu.org
mailing list for the GCC project.
[Bug libgcj/26487] Weird handling of HTTP Headers
- From: "ifoox at redhat dot com" <gcc-bugzilla at gcc dot gnu dot org>
- To: gcc-bugs at gcc dot gnu dot org
- Date: 28 Feb 2006 16:26:18 -0000
- Subject: [Bug libgcj/26487] Weird handling of HTTP Headers
- References: <bug-26487-12276@http.gcc.gnu.org/bugzilla/>
- Reply-to: gcc-bugzilla at gcc dot gnu dot org
------- Comment #5 from ifoox at redhat dot com 2006-02-28 16:26 -------
Having looked at the Javadoc for these functions, Mark's description is
correct. Only that the function names are getHeaderField(int) (and
getHeaderFieldKey(int)), getHeaderField(String), and getHeaderFields().
I've changed the testcase to use the gnome bugzilla which does not use https.
Here we get 3 headers for Set-Cookie instead of 2.
I've also changed the test case to also try to use
getHeaderField("Set-Cookie"), with libgcj I get all three headers that have the
name "Set-Cookie":
Bugzilla_login=110573; path=/, Bugzilla_logincookie=E11DnsKscK; path=/,
DEFAULTFORMAT=short; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
While Sun returns only the last one:
DEFAULTFORMAT=short; path=/; expires=Fri, 01-Jan-2038 00:00:00 GMT
The three headers were:
Set-Cookie: 'Bugzilla_login=110573; path=/'
Set-Cookie: 'Bugzilla_logincookie=yFd0huFJ3I; path=/'
Set-Cookie: 'DEFAULTFORMAT=short; path=/; expires=Fri, 01-Jan-2038
00:00:00 GMT'
I've changed the
--
http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26487