From: Henri Menke <henrimenke@gmail.com>
To: ntg-context@ntg.nl
Subject: Re: Files on a server
Date: Wed, 16 May 2018 22:41:22 +1200 [thread overview]
Message-ID: <866b81fb-8850-f813-fc48-ed101772028c@gmail.com> (raw)
In-Reply-To: <69D183B2-1264-4399-A805-591A82569287@ziggo.nl>
On 05/16/2018 09:31 PM, Hans van der Meer wrote:
> I tried to determine the existence of a file on the internet. See the
> following macro call:
>
> % Test if file exists.
> \edef\theurl{\linkprotocol://\urlbase\xmlatt{#1}{link}\thesuffix}
> \doiffileelse
> {\theurl}
> {\verbose{HVDM-PEV-TEST}{file exists: \theurl}}
> {\verbose{HVDM-PEV-TEST}{file does not exist: \theurl}}
>
> It seems that \doiffileelse always results in true except for local
> files where nonexistence is correctly handled.
>
> For example the following url definitely does not exist but nevertheless
> \doiffileelse reports its existence:
> HVDM-PEV-TEST > file exists:
> http://hansvandermeer.myqnapcloud.com/archive/denhaag/hga-dtb-1869-6040.pdf
>
> Is it possible that the \doiffile macros are extended for files on the
> internet or a correponding set \doifurl is developed?
I'm not speaking for the devs here, but I don't think that this is going
to be included. It would require that all webpages send proper 404
codes and timeout after reasonable delay. Also how would you handle
redirects? Should the ConTeXt run be stalled because checking for a
files existence on the web is caught in a redirect loop?
>
> Hans van der Meer
>
>
>
> ___________________________________________________________________________________
> 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
> ___________________________________________________________________________________
>
___________________________________________________________________________________
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-16 10:41 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 [this message]
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
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=866b81fb-8850-f813-fc48-ed101772028c@gmail.com \
--to=henrimenke@gmail.com \
--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).