netfilter-devel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jan Engelhardt <jengelh@inai.de>
To: Harald Welte <laforge@gnumonks.org>
Cc: Pablo Neira Ayuso <pablo@netfilter.org>,
	netfilter@vger.kernel.org, netfilter-devel@vger.kernel.org
Subject: Re: [MAINTENANCE] Shutting down FTP services at netfilter.org
Date: Wed, 3 Jun 2020 20:10:35 +0200 (CEST)	[thread overview]
Message-ID: <nycvar.YFH.7.77.849.2006032004220.24581@n3.vanv.qr> (raw)
In-Reply-To: <20200603171621.GC717800@nataraja>


On Wednesday 2020-06-03 19:16, Harald Welte wrote:
>
>On Wed, Jun 03, 2020 at 01:37:12PM +0200, Pablo Neira Ayuso wrote:
>> So netfilter.org will also be shutting down FTP services by
>> June 12th 2020.
>
>I always find that somewhat sad, as with HTTP there is no real convenient
>way to get directory listings in a standardized / parseable format.

There was convention, but no standard.
Which is just like what the default directory index modules of the httpd
implementations are.

>I think the important part would be some way to conveniently obtain a
>full clone, e.g. by rsync.  This way both public and private mirrors
>can exist in an efficient way, without having to resort to 'wget -r'
>or related hacks, which then only use file size as an indication if a
>file might have changed, ...

For completeness though, there is the "Last-Modified" HTTP header (similar to
what rsync bases its heuristic on). rsync is of course always preferable..

  reply	other threads:[~2020-06-03 18:10 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-06-03 11:37 [MAINTENANCE] Shutting down FTP services at netfilter.org Pablo Neira Ayuso
2020-06-03 17:16 ` Harald Welte
2020-06-03 18:10   ` Jan Engelhardt [this message]
2020-06-23  2:37     ` Trent W. Buck
2020-06-03 21:32   ` Pablo Neira Ayuso

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=nycvar.YFH.7.77.849.2006032004220.24581@n3.vanv.qr \
    --to=jengelh@inai.de \
    --cc=laforge@gnumonks.org \
    --cc=netfilter-devel@vger.kernel.org \
    --cc=netfilter@vger.kernel.org \
    --cc=pablo@netfilter.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).