Comment 6 for bug 1945663

As Ian as explained the store APIs and assertion use sometimes different formatting for what is the same value. The value is the same and converting is easily done programmatically.

Snapd here made the header consistent with the store API instead of the assertion, both approaches are reasonable. The identical naming of the field with the assertion is just a coincidence BTW, as the "Snap-" in the header is just a generic prefix used by snapd, instead of meaning "of the snap".

So while we can document the current formatting situation, we won't change the header formatting because that would make sense only if the store would change its formatting, but both would be be backward incompatible at this point.

So once the documentation has been improved this will be marked as "Won't fix".