* WGs marked with an * asterisk has had at least one new draft made available during the last 5 days

Ticket #317 (closed design: fixed)

Opened 3 years ago

Last modified 3 years ago

Cache-Control directive case sensitivity

Reported by: mnot@pobox.com Owned by: draft-ietf-httpbis-p6-cache@tools.ietf.org
Priority: normal Milestone: 17
Component: p6-cache Severity: Active WG Document
Keywords: Cc:
Origin: http://www.w3.org/mid/4560B97B-A55B-4B67-BAB8-CF82E1F5B900@mnot.net

Description

Currently, all of the cache-control directives (e.g., max-age) are defined as BNF strings, which means that they're case-insensitive.

However, theoretically someone could define a directive without using a string (as we do for some other constructs, e.g., the HTTP version identifier), which means that it'd be case-sensitive.

It seems that having such exceptions would be surprising, and that the most straightforward thing to do would be to define CC directive names as case-insensitive.

Change History

comment:1 Changed 3 years ago by mnot@pobox.com

From [1449]:

Clarify case insensitivity of CC directives. Addresses #317.

comment:2 Changed 3 years ago by mnot@pobox.com

  • Status changed from new to closed
  • Resolution set to incorporated

comment:3 Changed 3 years ago by mnot@pobox.com

  • Milestone changed from unassigned to 17

comment:4 Changed 3 years ago by mnot@pobox.com

  • Status changed from closed to reopened
  • Resolution incorporated deleted

comment:5 Changed 3 years ago by mnot@pobox.com

  • Status changed from reopened to closed
  • Resolution set to fixed
Note: See TracTickets for help on using tickets.