In 3 The Alt-Svc HTTP Header Field, there's:
When an Alt-Svc response header field is received from an origin, its value invalidates and replaces all cached alternative services for that origin.
However, in several other places, we now say that multiple alternatives can co-exist (with the client figuring out which to use).
Is this still our intent -- i.e., that the header field has a special cache invalidation semantic -- or is it just left over from our previous approach?
In 3 The Alt-Svc HTTP Header Field, there's:
However, in several other places, we now say that multiple alternatives can co-exist (with the client figuring out which to use).
Is this still our intent -- i.e., that the header field has a special cache invalidation semantic -- or is it just left over from our previous approach?