From: Chuck Hallenbeck <chuckhallenbeck@gmail.com>
To: Karl Dahlke <eklhad@comcast.net>
Cc: edbrowse-dev@lists.the-brannons.com
Subject: Re: [Edbrowse-dev] Curl library error
Date: Mon, 29 Jan 2018 10:19:56 -0500 (EST) [thread overview]
Message-ID: <alpine.DEB.2.21.1801291016450.3845@debian.pulsar.com> (raw)
In-Reply-To: <20180029090647.eklhad@comcast.net>
Karl,
when i do:
curl "https://www.literotica.com/stories/new_submissions.php"
I get a response consisting of 450 lines, about 56K bytes, which I
captured but have not yet examined. I think I have been shrinking
lately: More and more things are way over my head!
Chuck
--
Here too, In Northeast Ohio, The Moon is Waxing Gibbous (95% of Full)
When your only tool is a hammer, everything looks like a nail.
Sent from Erica's iPhone.
next prev parent reply other threads:[~2018-01-29 15:19 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-01-29 12:09 Chuck Hallenbeck
2018-01-29 14:06 ` Karl Dahlke
2018-01-29 15:19 ` Chuck Hallenbeck [this message]
2018-01-29 15:27 ` Chuck Hallenbeck
2018-01-29 16:03 ` Karl Dahlke
2018-01-29 16:53 ` Chuck Hallenbeck
2018-01-29 17:37 ` Dominique Martinet
[not found] ` <alpine.DEB.2.21.1802010449280.1929@debian.pulsar.com>
2018-02-01 18:08 ` 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=alpine.DEB.2.21.1801291016450.3845@debian.pulsar.com \
--to=chuckhallenbeck@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).