public inbox for java-prs@sourceware.org help / color / mirror / Atom feed
From: "mark at gcc dot gnu dot org" <gcc-bugzilla@gcc.gnu.org> To: java-prs@gcc.gnu.org Subject: [Bug libgcj/26487] Weird handling of HTTP Headers Date: Tue, 28 Feb 2006 11:38:00 -0000 [thread overview] Message-ID: <20060228113813.19483.qmail@sourceware.org> (raw) In-Reply-To: <bug-26487-12276@http.gcc.gnu.org/bugzilla/> ------- Comment #4 from mark at gcc dot gnu dot org 2006-02-28 11:38 ------- Confirmed. It looks like getHeader(int), getHeader(String) and getHeaders() have slightly different semantics. Where the first should return the actual n-th header field value only, the second should return the value of the last header with that name and the third should return a list of all values for that header. This seems slightly related to the bug just fixed by David Daney (bug #25851). Adding him and Chris to the CC since they might know more about how to adopt the design to support all three different semantics efficiently. P.S. The testcase will not work at the moment against classpath CVS since it is using a https URL, but Raif already has a patch for that which should hopefully go through all the testing soon. -- mark at gcc dot gnu dot org changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |dog at gnu dot org, mark at | |gcc dot gnu dot org, ddaney | |at avtrex dot com Status|UNCONFIRMED |NEW Ever Confirmed|0 |1 Last reconfirmed|0000-00-00 00:00:00 |2006-02-28 11:38:10 date| | http://gcc.gnu.org/bugzilla/show_bug.cgi?id=26487
next prev parent reply other threads:[~2006-02-28 11:38 UTC|newest] Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top 2006-02-27 21:34 [Bug libgcj/26487] New: " ifoox at redhat dot com 2006-02-27 21:42 ` [Bug libgcj/26487] " ifoox at redhat dot com 2006-02-27 21:44 ` ifoox at redhat dot com 2006-02-27 21:47 ` ifoox at redhat dot com 2006-02-28 11:38 ` mark at gcc dot gnu dot org [this message] 2006-02-28 16:26 ` ifoox at redhat dot com 2006-02-28 16:27 ` ifoox at redhat dot com 2006-02-28 16:54 ` daney at gcc dot gnu dot org 2006-02-28 22:05 ` daney at gcc dot gnu dot org 2006-03-01 16:11 ` ifoox at redhat dot com 2006-03-01 17:10 ` ddaney at avtrex dot com 2006-03-01 18:10 ` ifoox at redhat dot com 2006-03-03 23:24 ` daney at gcc dot gnu dot org 2006-03-03 23:25 ` [Bug classpath/26487] " daney at gcc dot gnu dot org
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20060228113813.19483.qmail@sourceware.org \ --to=gcc-bugzilla@gcc.gnu.org \ --cc=java-prs@gcc.gnu.org \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).