caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: Gerd Stolpmann <info@gerd-stolpmann.de>
To: Simon Cruanes <simon.cruanes.2007@m4x.org>,
	Alan Schmitt <alan.schmitt@polytechnique.org>
Cc: Christophe TROESTLER <Christophe.TROESTLER@umons.ac.be>,
	Gerd Stolpmann <info@gerd-stolpmann.de>,
	OCaml Mailing List <caml-list@inria.fr>
Subject: Re: [Caml-list] https and Ocamlnet
Date: Thu, 26 Sep 2019 17:44:59 +0200	[thread overview]
Message-ID: <e2ad61f1-05fc-46c6-9127-f09d37b58681@gerd-stolpmann.de> (raw)
In-Reply-To: <20190926134158.GC1781@carty>


[-- Attachment #1.1: Type: text/plain, Size: 1868 bytes --]


Am 26.09.19 um 15:41 schrieb Simon Cruanes:
> I've been working on higher level bindings to cURL (based on ocurl), at
> https://github.com/c-cube/ezcurl .
>
> ```
> $ dune utop src/sync
> # Ezcurl.get ~url:"https://ocaml.org/feed.xml" ();;
> - : (Ezcurl_core.response, Curl.curlCode * string) result =
> Ok
>  {Ezcurl_core.code = 200;
>   headers =
>    [("Content-Type", "application/xml"); ("Accept-Ranges", "bytes");
>     ("ETag", "\"1394832364\"");
>     ("Last-Modified", "Thu, 26 Sep 2019 13:15:03 GMT");
>     ("Content-Length", "402487");
>     ("Date", "Thu, 26 Sep 2019 13:49:00 GMT");
>     ("Server", "lighttpd/1.4.53")];
>   body =
>    "<?xml version=\"1.0\" encoding=\"UTF-8\"?>\n<feed xmlns=\"http://www.w3.org/2005/Atom\"><icon>http://ocaml.org/img/colour-icon-170x148.png</icon><generator uri=\"https://ocaml.org/\" version=\"${version:syndic}\">OCaml Syndic.Atom feed aggregator</generator><id>urn:md5:302d717d0937d8"... (* string length 402487; truncated *);
>   info =
>    {Ezcurl_core.ri_response_time = 6.346256; ri_redirect_count = 0}}
> ```
>
> Maybe it's a different version of GNUTLS though (I'm on archlinux, it's 3.6.9-1).

Don't think so, because gnutls-cli can actually connect to ocaml.org. I
rather guess it's a protocol option that's creating the problems, in
particular one that changes the order of reads and writes on the socket
(so it's visible to the wrapping library). BTW, it's not only ocaml.org
but e.g. also google.com.

Gerd

-- 
------------------------------------------------------------
Gerd Stolpmann, Darmstadt, Germany    gerd@gerd-stolpmann.de
My OCaml site:          http://www.camlcity.org
Contact details:        http://www.camlcity.org/contact.html
Company homepage:       http://www.gerd-stolpmann.de
------------------------------------------------------------



[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

  reply	other threads:[~2019-09-26 15:45 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-25 13:49 Alan Schmitt
2019-09-25 14:52 ` Christophe TROESTLER
2019-09-25 15:47 ` Gerd Stolpmann
2019-09-26  6:20   ` Alan Schmitt
2019-09-26  6:27     ` Christophe TROESTLER
2019-09-26  6:56       ` Alan Schmitt
2019-09-26 13:41         ` Simon Cruanes
2019-09-26 15:44           ` Gerd Stolpmann [this message]
2019-09-27  6:31           ` Alan Schmitt
2019-09-27 13:53             ` Simon Cruanes
2019-09-26 14:39         ` Adrien Nader
2019-09-25 17:38 ` Oliver Bandel
2019-12-29 13:42 ` Oliver Bandel

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=e2ad61f1-05fc-46c6-9127-f09d37b58681@gerd-stolpmann.de \
    --to=info@gerd-stolpmann.de \
    --cc=Christophe.TROESTLER@umons.ac.be \
    --cc=alan.schmitt@polytechnique.org \
    --cc=caml-list@inria.fr \
    --cc=simon.cruanes.2007@m4x.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 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).