topic
Verified 2026-09-18Legacy HTTP Value Migration
Deprecated and obsolete registry values remain useful for compatibility diagnosis but should not silently become new defaults.
Classify legacy values at the boundary, document their replacement, and remove them from new responses after measuring client compatibility. Preserve wire compatibility only as long as the risk and support contract justify it.
httplegacymigrationsecuritycache
Reference (http)
Pragma: no-cache Cache-Control: no-cache Public-Key-Pins: pin-sha256="..."
Classify legacy values at the boundary, document their replacement, and remove them from new responses after measuring client compatibility. Preserve wire compatibility only as long as the risk and support contract justify it.
Common mistakes
- Keeping obsolete values forever because they are harmless-looking, or removing them without checking old clients and intermediary behavior.