Warning

[mnot]

Isn't implemented, generated, used or surfaced to users; can we deprecate?

[mnot]

Proposal:

• Replace 5.5 Warning with a section noting that the Warning header is deprecated, and should be ignored.
• Remove all requirements to generate Warning
• Remove Warning-specific requirements in 3.3 Combining Partial Content
• Remove Warning-specific requirements in 4.3.4 Freshening Stored Responses upon Validation
• Remove Warning-specific requirements in 4.3.5 Freshening Responses via HEAD

[royfielding]

+1, with big notes in the Changes section.

[sordina]

Just curious if anyone has any background, what would be a good alternative to the Warning header for cache limit warnings?

[royfielding]

Just curious if anyone has any background, what would be a good alternative to the Warning header for cache limit warnings?

This isn't a good place for general discussion. You might want to ask the mailing list, though I am not aware of any cache limit warnings within HTTP because they are only relevant to the cache admin (who typically has an email or phone number stored for such notifications).