public inbox for gcc-prs@sourceware.org help / color / mirror / Atom feed
From: francis@ecal.com To: java-gnats@sourceware.cygnus.com Subject: libgcj/1164: Falsely claims HTTP/1.1 compliance Date: Wed, 20 Dec 2000 12:21:00 -0000 [thread overview] Message-ID: <20000309184703.26263.qmail@sourceware.cygnus.com> (raw) >Number: 1164 >Category: libgcj >Synopsis: Falsely claims HTTP/1.1 compliance >Confidential: no >Severity: serious >Priority: medium >Responsible: warrenl >State: closed >Class: sw-bug >Submitter-Id: net >Arrival-Date: Wed Dec 20 12:16:38 PST 2000 >Closed-Date: Thu Aug 10 02:14:19 PDT 2000 >Last-Modified: Thu Aug 10 02:16:01 PDT 2000 >Originator: francis@ecal.com >Release: unknown-1.0 >Organization: >Environment: RedHat 6.1 >Description: gnu.gcj.protocol.http.Connection tells the server it's an HTTP/1.1 client, but it isn't; it doesn't support chunked Transfer-Encoding (or persistent connections, or pretty much anything else). If you talk to an HTTP/1.1 server (e.g., Apache), and it uses the chunked Transfer- Encoding, you wind up with the chunking data mixed in with the response content. >How-To-Repeat: Compile and run the attached Java program, which fetches a PHP-generated URL (a single line, saying "See?"). The URL is delivered chunked, and so the program prints out all the chunking information (plus the headers; I'm getting ready to put in another bug on that). >Fix: I hope to work on full 1.1 support; but, in the meantime, I recommend changing line 97 of libjava/gnu/gcj/protocol/http/Connection.java to say "HTTP/1.0" instead of "HTTP/1.1". >Release-Note: >Audit-Trail: Formerly PR java.net/169 State-Changed-From-To: open->closed State-Changed-By: bryce State-Changed-When: Thu Aug 10 02:14:19 2000 State-Changed-Why: I checked in a fix for this: http://sources.redhat.com/ml/java-patches/2000-q3/msg00096.html From: bryce@albatross.co.nz To: francis@ecal.com, java-gnats@sourceware.cygnus.com, warrenl@cygnus.com Cc: Subject: Re: java.net/169 Date: 10 Aug 2000 09:14:19 -0000 Synopsis: Falsely claims HTTP/1.1 compliance State-Changed-From-To: open->closed State-Changed-By: bryce State-Changed-When: Thu Aug 10 02:14:19 2000 State-Changed-Why: I checked in a fix for this: http://sources.redhat.com/ml/java-patches/2000-q3/msg00096.html http://sources.redhat.com/cgi-bin/gnatsweb.pl?cmd=view&pr=169&database=java >Unformatted: ----gnatsweb-attachment---- Content-Type: application/octet-stream; name="DemonstrateChunked.java" Content-Transfer-Encoding: base64 Content-Disposition: attachment; filename="DemonstrateChunked.java" aW1wb3J0IGphdmEubmV0Lio7CmltcG9ydCBqYXZhLmlvLio7CgpwdWJsaWMgY2xhc3MgRGVtb25z dHJhdGVDaHVua2VkIHsKICAgIHB1YmxpYyBzdGF0aWMgdm9pZCBtYWluKFN0cmluZyBhcmdzW10p CiAgICB7CglVUkwgdXJsOwoKCXRyeSB7CgkgICAgdXJsPW5ldyBVUkwoImh0dHA6Ly9pbXBwLnJl c2VhcmNoLmVjYWwuY29tL2RlbW9uc3RyYXRlLnBocDMiKTsKCX0gY2F0Y2ggKGphdmEubmV0Lk1h bGZvcm1lZFVSTEV4Y2VwdGlvbiBtYWxmKSB7CgkgICAgU3lzdGVtLmVyci5wcmludGxuKCJNYWxm b3JtZWQgVVJMOiAiK21hbGYuZ2V0TWVzc2FnZSgpKTsKCSAgICByZXR1cm47Cgl9CgoJRGF0YUlu cHV0U3RyZWFtIGluOwoKCXRyeSB7CgkgICAgVVJMQ29ubmVjdGlvbiBjb25uPXVybC5vcGVuQ29u bmVjdGlvbigpOwoJICAgIElucHV0U3RyZWFtIF9pbj1jb25uLmdldElucHV0U3RyZWFtKCk7Cgkg ICAgaW49bmV3IERhdGFJbnB1dFN0cmVhbShfaW4pOwoJfSBjYXRjaCAoSU9FeGNlcHRpb24gaW8p IHsKCSAgICBTeXN0ZW0uZXJyLnByaW50bG4oIkNhbid0IGZldGNoIFVSTDogIitpby5nZXRNZXNz YWdlKCkpOwoJICAgIHJldHVybjsKCX0KCglTdHJpbmcgbGluZTsKCXRyeSB7CgkgICAgd2hpbGUg KChsaW5lPWluLnJlYWRMaW5lKCkpIT1udWxsKQoJCVN5c3RlbS5vdXQucHJpbnRsbihsaW5lKTsK CX0gY2F0Y2ggKElPRXhjZXB0aW9uIGlvKSB7CgkgICAgU3lzdGVtLm91dC5wcmludGxuKCJDYW4n dCByZWFkIGxpbmUgZnJvbSBVUkw6ICIraW8uZ2V0TWVzc2FnZSgpKTsKCSAgICByZXR1cm47Cgl9 CiAgICB9Cn07Cg==
reply other threads:[~2000-12-20 12:21 UTC|newest] Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20000309184703.26263.qmail@sourceware.cygnus.com \ --to=francis@ecal.com \ --cc=java-gnats@sourceware.cygnus.com \ /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).