No I haven't looked at adding/adjusting tests, but I should. This patch was
inspired by a news story about a gopher server restarting operations, so I
thought I'd try to connect. My perception of what followed (as determined
by writing code that I thought should work, observing results, tcpdump
What I suspect that original code was going was parsing the content
from a gopher server (and in fact, taking some shortcuts that may have
happened to work for original use-case). The actual URI is the second
component of an appropriate gopher line, and to be used unadulterated.
What I think
On Fri, 26 Feb 2016, bch wrote:
You're probably right, re: "the number of people using gopher with
(lib)curl" --I was wondering if there was deep knowledge contained by you
(@bagder) or anybody else...
I wrote the first gopher code before curl was even called curl, back in 1997
or
. If there are yet other tab delimited fields, the basic
Gopher client should ignore them. A CR LF denotes the end of the
item.
You're probably right, re: "the number of people using gopher with
(lib)curl" --I was wondering if there was deep knowledge contained by
you (@bagder) or an
On Fri, 26 Feb 2016, bch wrote:
...and I'm seeing what appears to be poor gopher URI handling:
It just shows how many people are actually using gopher with (lib)curl
or am I misinterpetting what the URI really ought to be?
Is there anyone around who still remembers how gopher URLs should
characters up to the tab form a user display string to be
shown to the user for use in selecting this document (or directory)
for retrieval. The first character of the line is really defining
the type of item described on this line. In nearly every case, the
Gopher client software will give
...and I'm seeing what appears to be poor gopher URI handling:
$ curl gopher://gopher.metafilter.com/Music/Auld-Lang-Syne.html
3'/usic/Auld-Lang-Syne.html' does not exist (no handler found)
error.host 1
or am I misinterpetting what the URI really ought to be?
-bch
On 2/26/16, bch
Hi,
I added gopher: support to NetSurf last week, cf. my branch:
http://source.netsurf-browser.org/branches/mmu_man/netsurf-gopher-support/
... and it works not too bad, though I still have some issues with some
selectors that libcurl seems to convert to Gopher+ without being told
For example the pages about Bucktooth:
gopher://gopher.floodgap.com/1/buck/dbrowse?glossary
gopher://gopher.floodgap.com/1/buck/dbrowse?faquse
return items with an extra tab screwing up the urls to something like:
gopher://faquse?1:gopher.floodgap.com/0/buck/dbrowse
Nice spot, you
On Thu, 28 Apr 2011, François Revol wrote:
Also, gopher should probably be made a default in curl's configure since it
doesn't imply any dependency, as I had to hack around with the MacPort file
to add --enable-gopher (and force NetSurf to find this one instead of
Apple's old one), and it's
On Thu, 28 Apr 2011, François Revol wrote:
I didn't find any public SCM, would be easier to supply patches...
See http://curl.haxx.se/dev/source.html
--
/ daniel.haxx.se---
List admin:
Le 28 avr. 2011 à 16:50, Daniel Stenberg a écrit :
On Thu, 28 Apr 2011, François Revol wrote:
Also, gopher should probably be made a default in curl's configure since it
doesn't imply any dependency, as I had to hack around with the MacPort file
to add --enable-gopher (and force NetSurf
Le 28 avr. 2011 à 17:01, François Revol a écrit :
I didn't find any public SCM, would be easier to supply patches...
Forget it, it was blatantly apparent on the right side, I need to change
glasses :D
François.
---
List admin:
Upon further review, this is actually a bug in the *server,* not *curl*. Since
the server is my code, I will issue a fix for bucktooth. Thanks for the
report!
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com
Okay, here we go. This is gopher for cURL round 2:
Thanks a lot for your contribution! I've just merged your patches with these
additional changes by me:
* converted the tests to instead use the HTTP server (with a --gopher
switch) to make them work better
* prevented a busy-loop
On Mon, 23 Aug 2010, Cameron Kaiser wrote:
Okay, here we go. This is gopher for cURL round 2:
Great, thanks.
I consider this to be good enough to get merged. I'm just working on polishing
up some details, then I intend to merge these into mainline and provide you
with feedback for what
Okay, here we go. This is gopher for cURL round 2:
Great, thanks.
I consider this to be good enough to get merged. I'm just working on
polishing up some details, then I intend to merge these into mainline and
provide you with feedback for what probably is the last outstanding nit.
Hang
Okay, here we go. This is gopher for cURL round 2:
-- Curl_write() now used for the critical portion in lib/gopher.c
-- ftpserver.pl modified to serve Gopher over IPv4 and IPv6
-- four base tests for gopher, including index, selector, query and IPv6
I spoke with Daniel offlist and wrote up initial support for the Gopher
protocol this week. While Gopher may be an antiquated protocol for many,
there are still around 150 active servers still out there, it is a simple
alternative for file collections, it makes cURL increasingly more
comprehensive
And one more, to remove my irritated little outburst in url.c when trying
to figure out what the protocol mask should be.
--
personal: http://www.cameronkaiser.com/ --
Cameron Kaiser * Floodgap Systems * www.floodgap.com * ckai...@floodgap.com
-- The less
the Curl_add_buffer_init(), Curl_add_bufferf() and
Curl_add_buffer_send() which is done by the HTTP code to send requests. It
will probably require some further adjustments of the gopher code to look more
HTTPish or for the Curl_add_buffer-functions to become slightly more
generic...
2 - One
() and
Curl_add_buffer_send() which is done by the HTTP code to send requests.
It will probably require some further adjustments of the gopher code to look
more HTTPish or for the Curl_add_buffer-functions to become slightly more
generic...
Wilco. I'll tweak that section.
2 - One of the primary
22 matches
Mail list logo
