Skip to content

no-vary: URI/URL/Caching terminology (fixes #3283) #3284

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

no-vary: URI/URL/Caching terminology (fixes #3283) #3284

wants to merge 1 commit into from

Conversation

@reschke
Copy link
Contributor

@reschke reschke commented Oct 14, 2025

This is an attempt (probably incomplete) to clean up terminology of URIs vs URLs vs resources vs responses etc.

IMHO the goal should be:

  • use URL when referencing algorithms and formats in the WHATWG spec,
  • use URI when talking about HTTP, Caching and related topics.

...and also explain what's going on wrt this.

@reschke reschke changed the title no-vary: URI/URL/Caching terminology no-vary: URI/URL/Caching terminology (fixes #3283) Oct 14, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@domenic domenic Awaiting requested review from domenic domenic is a code owner

@jeremyroman jeremyroman Awaiting requested review from jeremyroman jeremyroman is a code owner

Assignees

No one assigned

Labels

editorial no-vary-search

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@reschke