From: Hans Hagen <j.hagen@xs4all.nl>
To: ntg-context@ntg.nl
Subject: Re: Files on a server
Date: Thu, 17 May 2018 10:42:16 +0200 [thread overview]
Message-ID: <75fbea77-2afc-572c-cf7f-2a582b6bbeaa@xs4all.nl> (raw)
In-Reply-To: <4E2F21A0-AAE3-49B4-B8F5-75D94B6FCA5D@elvenkind.com>
On 5/17/2018 9:54 AM, Taco Hoekwater wrote:
>
>
>> On 17 May 2018, at 09:39, Taco Hoekwater <taco@elvenkind.com> wrote:
>>
>>
>>
>>> On 17 May 2018, at 09:32, Ulrike Fischer <news3@nililand.de> wrote:
>>>
>>> Am Wed, 16 May 2018 14:23:42 +0200 schrieb Taco Hoekwater:
>>>
>>>> Or use luasocket, which is included in the luatex binary:
>>>
>>> But I'm right that this works only with http and not with https?
>>
>> Works ok for me. Did you test?
>
> Oh, sorry. It seems it is sneakily rewriting the https:// to http://,
> and so does not _actually_ work. Which makes sense, now that I think
> about it. Doing https would need openssl support, which is unlikely to
> ever be built into luatex.
>
> Sorry for being misleading,
i have (among a few others such experiments) a util-crl.lua file that
uses libcurl (using ffi) because it's one of the things we used to test
ffi support in luatex
i didn't add that to the distribution because i'm not sure what libname
on windows to use (mojca and i discussed the option to ship some libs
with the garden distribition at some time) and i don't want to end up in
endless discussions about lib names on systems
some day i might add this one (if the right lib is found it works ok ..
performance on my old laptop is is 5000 https://tug.org pages in 100
sec, 5000 pragma website main pages in 70 sec)
(fwiw: i do use curl but just call the binary which in practice is just
as efficient because one seldom does a lot in a run)
(and i use the socket lib for other things)
Hans
-----------------------------------------------------------------
Hans Hagen | PRAGMA ADE
Ridderstraat 27 | 8061 GH Hasselt | The Netherlands
tel: 038 477 53 69 | www.pragma-ade.nl | www.pragma-pod.nl
-----------------------------------------------------------------
___________________________________________________________________________________
If your question is of interest to others as well, please add an entry to the Wiki!
maillist : ntg-context@ntg.nl / http://www.ntg.nl/mailman/listinfo/ntg-context
webpage : http://www.pragma-ade.nl / http://context.aanhet.net
archive : https://bitbucket.org/phg/context-mirror/commits/
wiki : http://contextgarden.net
___________________________________________________________________________________
next prev parent reply other threads:[~2018-05-17 8:42 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-05-16 9:31 Hans van der Meer
2018-05-16 10:41 ` Henri Menke
2018-05-16 11:23 ` Hans van der Meer
2018-05-16 11:45 ` Henri Menke
2018-05-16 12:23 ` Taco Hoekwater
2018-05-16 12:58 ` Hans van der Meer
2018-05-16 13:41 ` Hans Hagen
2018-05-16 14:05 ` Taco Hoekwater
2018-05-17 7:32 ` Ulrike Fischer
2018-05-17 7:39 ` Taco Hoekwater
2018-05-17 7:52 ` Hans van der Meer
2018-05-17 7:54 ` Taco Hoekwater
2018-05-17 8:30 ` Ulrike Fischer
2018-05-17 8:42 ` Hans Hagen [this message]
2018-05-17 8:46 ` luigi scarso
2018-05-17 8:20 ` Ulrike Fischer
2018-05-17 8:31 ` Taco Hoekwater
2018-05-17 9:03 ` Taco Hoekwater
2018-05-17 9:49 ` Henri Menke
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=75fbea77-2afc-572c-cf7f-2a582b6bbeaa@xs4all.nl \
--to=j.hagen@xs4all.nl \
--cc=ntg-context@ntg.nl \
/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).