From: Oliver Bandel <oliver@first.in-berlin.de>
To: caml-list@inria.fr
Subject: Re: [Caml-list] OCamlnet: handling TLS-errors
Date: Thu, 02 Aug 2018 22:58:16 +0200 [thread overview]
Message-ID: <20180802225816.Horde.mOhld_iOSYDjylRzvpSMJoE@webmail.in-berlin.de> (raw)
In-Reply-To: <20180702012943.Horde.jlAWicnynJ1OLBwxZ2e3814@webmail.in-berlin.de>
...see below.
Zitat von Oliver Bandel <oliver@first.in-berlin.de> (Mon, 02 Jul 2018
01:29:43 +0200)
> Hello,
>
> how to handle TLS-errors in OCamlnet?
>
> To be more specific on what the problem is:
> in some rare cases, accessing websites with OCamlnet throws the
> error GNUTLS_E_PREMATURE_TERMINATION.
>
> For security-sensible applications aborting the access would be best.
> In the use-case that I have, the TLS-error is not a problem, the
> data is not security-sensitive.
> (Webbrowsers just ignore this error and display the webpage without
> mourning.)
>
> What I want to do is, to access the data that was already read and use it.
> So I want to just "ignore"/"catch" the TLS-error.
>
> How to do that in OCamlnet?
>
> Is it necessary to write my own TLS-provider?
> And how would that look like?
>
> Regards,
> Oliver
Hello, here are some sources to test the issue:
https://www.first.in-berlin.de/mixed/ocamlnet-gnutls-error/
The zip-file contains the three other files.
Just "make" should compile the stuff.
Any help is welcome.
Ciao,
Oliver
--
Caml-list mailing list. Subscription management and archives:
https://sympa.inria.fr/sympa/arc/caml-list
Beginner's list: http://groups.yahoo.com/group/ocaml_beginners
Bug reports: http://caml.inria.fr/bin/caml-bugs
prev parent reply other threads:[~2018-08-02 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-07-01 23:29 Oliver Bandel
2018-08-02 20:58 ` Oliver Bandel [this message]
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=20180802225816.Horde.mOhld_iOSYDjylRzvpSMJoE@webmail.in-berlin.de \
--to=oliver@first.in-berlin.de \
--cc=caml-list@inria.fr \
/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).