New format in "etag" response header in 3.66.0

Hi,

Our team recently upgraded to OSS 3.66.0, and discovered a format change in the “etag” response header>

Old format (<= 3.65.0):
“{SHA1{18578ef02384f87026308877657b517c4404a915}}”

New format (>= 3.66.0):
“18578ef02384f87026308877657b517c4404a915”

Since we can’t find any documentation for this, we’re reaching out to ask if this is an intentional and permanent change?

Best regards,
Marius Stenbek

Hi Marius,

I’d just point out that etags by the RFC are an opaque identifier so I would generally discourage you from having any expectations about the content of the header.