edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Adam Thompson <arthompson1990@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: Edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Unwind
Date: Tue, 30 Dec 2014 11:23:18 +0000	[thread overview]
Message-ID: <20141230112318.GA9985@spoons.adamthompson.me.uk> (raw)
In-Reply-To: <20141129235510.eklhad@comcast.net>

[-- Attachment #1: Type: text/plain, Size: 945 bytes --]

On Mon, Dec 29, 2014 at 11:55:10PM -0500, Karl Dahlke wrote:
> > large iso image through ssl
> > https://archive.torproject.org/amnesia.boum.org/tails/stable/tails-i386-1.2.2/tails-i386-1.2.2.iso
> 
> And indeed, it doesn't work, which is what I feared.
> I suppose something in the disconnect process from the parent disrupts
> the ssl connection so that the child cannot continue.
> The error is:
> 
> could not read the data from the server

Ah ok, I'm not entirely surprised. It could be a number of things,
but tbh I suspect that it's going to be difficult to get this to work.
Why don't you do a head request before the get? That way you would get just the headers and could prompt the user and possibly fork before beginning the download?
I suspect this is the cleanest design without getting into multi-threading.
Although it adds an extra round-trip, it'll probably not be that noticeable (if at all).

Cheers,
Adam.

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 473 bytes --]

  reply	other threads:[~2014-12-30 11:25 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-12-30  4:55 Karl Dahlke
2014-12-30 11:23 ` Adam Thompson [this message]
  -- strict thread matches above, loose matches on Subject: below --
2014-12-30  0:20 Karl Dahlke

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=20141230112318.GA9985@spoons.adamthompson.me.uk \
    --to=arthompson1990@gmail.com \
    --cc=Edbrowse-dev@lists.the-brannons.com \
    --cc=eklhad@comcast.net \
    /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 NNTP newsgroup(s).