From: Nick Clifton <nickc@redhat.com>
To: overseers@sourceware.org
Subject: Unable to upload object file tarball to bugzilla
Date: Mon, 14 Dec 2009 12:08:00 -0000 [thread overview]
Message-ID: <4B262AB4.6090209@redhat.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 896 bytes --]
Hi Guys,
I have been trying and failing to upload a compressed object file
tarball to PR 11088 in the sourceware bugzilla system. I fill out the
various fields in the attachment entry page, hit the submit button and
then get "Connection Interrupted - The connection to the server was
reset while the page was loading".
This is using Firefox 3, but I have also tried Internal Explorer and
Chrome with the same results. The tarball is not very big (26504
bytes), but I also tried an uncompressed version with the same results.
I have tried allowing the auto-detect method to determine the content
type as well as selecting "binary file" from the drop down menu - no dice.
I was able to upload a patch file to the PR, so there must be
something about my tarball that the system does not like. Any ideas ?
Cheers
Nick
PS. I have attached the tarball in case it helps.
[-- Attachment #2: objs.tar.bz2 --]
[-- Type: application/x-bzip, Size: 26504 bytes --]
reply other threads:[~2009-12-14 12:08 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=4B262AB4.6090209@redhat.com \
--to=nickc@redhat.com \
--cc=overseers@sourceware.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: link
Be 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).