Buy commercial curl support. We
help you work out your issues, debug your libcurl applications, use the API,
port to new platforms, add new features and more. With a team lead by the
curl founder Daniel himself.
%{filename_effective but not transmit file?
- Contemporary messages sorted: [ by date ] [ by thread ] [ by subject ] [ by author ] [ by messages with attachments ]
From: Paul Gilmartin via curl-users <curl-users_at_lists.haxx.se>
Date: Wed, 11 Sep 2024 17:47:50 -0600
Is it possible to get %{filename_effective without transmitting
the file? I'm trying to make the ETag name pend on that,
something like:
"--etag-compare %{filename_effectiv.etag"
So far, the best I can do is perform a trial fetch, directing
the output to a read-only directory, failing but returning
%{filename_ effective and using that in the real fetch.
is there a server-side TOCTTOU timing hazard? I'm imagining
a busy server which:
o declines to send a resource because of ETag match
o Updates the resource concurrently
o returns the ETag matching the new version.
The server should not return an ETag in the headers
different from the one which caused it not to send
a resource.
Date: Wed, 11 Sep 2024 17:47:50 -0600
Is it possible to get %{filename_effective without transmitting
the file? I'm trying to make the ETag name pend on that,
something like:
"--etag-compare %{filename_effectiv.etag"
So far, the best I can do is perform a trial fetch, directing
the output to a read-only directory, failing but returning
%{filename_ effective and using that in the real fetch.
is there a server-side TOCTTOU timing hazard? I'm imagining
a busy server which:
o declines to send a resource because of ETag match
o Updates the resource concurrently
o returns the ETag matching the new version.
The server should not return an ETag in the headers
different from the one which caused it not to send
a resource.
-- Thanks, gil -- Unsubscribe: https://lists.haxx.se/mailman/listinfo/curl-users Etiquette: https://curl.se/mail/etiquette.htmlReceived on 2024-09-12