Skip to content

Conversation

@guidiaz
Copy link

@guidiaz guidiaz commented Feb 22, 2024

No description provided.


While HTTP-GET and HTTP-POST data retrievals may cover the majority of use cases, other potential applications rather need to retrieve metadata from allegedly existing resource contents on the Internet, instead of relyng on calls to REST/API endpoints.

For instance, metadata like the existence, age, size, hash or the content type of some given URL, can be extracted by a single HTTP-HEAD retrieval, without actually forcing witnessing nodes to download the whole content that is being referred.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For me, this is the main point of allowing HTTP HEAD. We aren't unlocking a new feature but avoiding witnesses downloading unnecessary data. I'd emphasize that in the first paragraph of "Motivation and rationale".

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants