edbrowse-dev - development list for edbrowse
 help / color / mirror / Atom feed
From: Karl Dahlke <eklhad@comcast.net>
To: Edbrowse-dev@lists.the-brannons.com
Subject: [Edbrowse-dev] download background
Date: Sat, 10 Jan 2015 03:37:13 -0500	[thread overview]
Message-ID: <20150010033713.eklhad@comcast.net> (raw)

Further exploration of download in background fron a secure site:
I did finally get it to work, but I had to free all curl resources,
global cleanup, global init, and reset all the curl attributes
from start to the point of the https download.
But ... after the download, the child process was so corrupted
it couldn't even exit without seg fault.
I looked in curl.h and it says very clearly that
the global init function should be called "exactly once",
and the same for global cleanup.
Clearly I wasn't doing that, so all bets are off!
But that is the only way to get the secure download to work
in the child process.
I think this is a problem we can't solve or work around.
I also think it is primarily in ssl.
Nobody else seems to have this problem,
and I am on an older version of openssl,
so instead of spinning my wheels,
I think I should just document that download in background from secure sites
may not work on openssl version less than 1.0.1g,
and move on to other projects.
We've done this in other respects;
edbrowse just doesn't work with curl version < 7.26, or with pcre < something.
So I think this is reasonable, if indeed the problem is in ssl,
and fixed in recent versions of ssl.

Karl Dahlke

             reply	other threads:[~2015-01-10  8:39 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-01-10  8:37 Karl Dahlke [this message]
2015-01-10  9:43 ` Chris Brannon
2015-01-10 15:11   ` Adam Thompson
  -- strict thread matches above, loose matches on Subject: below --
2015-01-09 21:01 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=20150010033713.eklhad@comcast.net \
    --to=eklhad@comcast.net \
    --cc=Edbrowse-dev@lists.the-brannons.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: 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).