NetBSD Problem Report #59190

From www@netbsd.org  Mon Mar 17 15:34:00 2025
Return-Path: <www@netbsd.org>
Received: from mail.netbsd.org (mail.netbsd.org [199.233.217.200])
	(using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits)
	 key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256
	 client-signature RSA-PSS (2048 bits) client-digest SHA256)
	(Client CN "mail.NetBSD.org", Issuer "mail.NetBSD.org CA" (not verified))
	by mollari.NetBSD.org (Postfix) with ESMTPS id BA1591A9239
	for <gnats-bugs@gnats.NetBSD.org>; Mon, 17 Mar 2025 15:33:59 +0000 (UTC)
Message-Id: <20250317153358.91B2A1A923C@mollari.NetBSD.org>
Date: Mon, 17 Mar 2025 15:33:58 +0000 (UTC)
From: campbell+netbsd@mumble.net
Reply-To: campbell+netbsd@mumble.net
To: gnats-bugs@NetBSD.org
Subject: ftp(1): support server-controlled caching
X-Send-Pr-Version: www-1.0

>Number:         59190
>Category:       bin
>Synopsis:       ftp(1): support server-controlled caching
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    bin-bug-people
>State:          open
>Class:          change-request
>Submitter-Id:   net
>Arrival-Date:   Mon Mar 17 15:35:00 +0000 2025
>Originator:     Taylor R Campbell
>Release:        current
>Organization:
The CacheFTP Expiration
>Environment:
>Description:
It would be nice if you could do something like

ftp -o cachedata -c cachemeta https://example.com/url

and ftp(1) would consult cachemeta and stop if it indicates a fresh result, or query https://example.com/url and save information from any cache-control or expires directives in cachemeta at the same time as it saves the data in cachedata for the next time you run the same command.

RFC 7234: Hypertext Transfer Protocol (HTTP/1.1): Caching
https://www.rfc-editor.org/rfc/rfc7234.html
>How-To-Repeat:
write a script that fetches a seldom-changing data file like https://data.iana.org/rdap/dns.json every time
>Fix:
Yes, please!

Home	PR Database Search