From: Alan Perry <aperry@snowmoose.com>
To: Andrei Borzenkov <arvidjaar@gmail.com>
Cc: grub-devel@gnu.org
Subject: Re: Is anyone using the http module to do largish transfers?
Date: Sun, 08 Feb 2015 12:26:53 -0800 [thread overview]
Message-ID: <54D7C68D.9050600@snowmoose.com> (raw)
In-Reply-To: <20150207193517.50294beb@opensuse.site>
On 2/7/15 8:35 AM, Andrei Borzenkov wrote:
> В Wed, 04 Feb 2015 16:39:20 -0800
> Alan Perry <aperry@snowmoose.com> пишет:
>
>> Hi,
>>
>> I am trying to debug a problem involving largish HTTP data transfers
>> (around 80M). I have no problem transferring around 3M with the grub
>> http module. Has anyone here observed a similar issue or is this not a
>> problem for others and I should be looking for the problem somewhere
>> other than the http module?
> I did a quick test and was able to do "initrd (http)/initrd" for ~90MB
> file using current git. This is under QEMU. Physical hardware may be
> different.
OK, knowing that it works in some instances is good. As I have been
digging into the problem, it seems to be somewhere other than http. I
would elaborate further, but I am still working through why the code is
doing what I see on the network.
Another question about the http module. http_establish() builds a GET
request that may have a Content-Range header. However, looking at the
HTTP/1.1 RFCs, Content-Range is something that appears in a status 206
response, not in a request. The http module shouldn't insert this
header, should it?
alan
>
>> Thanks,
>>
>> alan
>>
>>
>> _______________________________________________
>> Grub-devel mailing list
>> Grub-devel@gnu.org
>> https://lists.gnu.org/mailman/listinfo/grub-devel
next prev parent reply other threads:[~2015-02-08 20:27 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-05 0:39 Is anyone using the http module to do largish transfers? Alan Perry
2015-02-07 16:35 ` Andrei Borzenkov
2015-02-08 20:26 ` Alan Perry [this message]
2015-02-09 3:24 ` Andrei Borzenkov
2015-02-09 4:29 ` Alan Perry
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=54D7C68D.9050600@snowmoose.com \
--to=aperry@snowmoose.com \
--cc=arvidjaar@gmail.com \
--cc=grub-devel@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: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.