On 30/01/15 17:45, Lester Caine wrote:
> On 30/01/15 14:22, Michael Wallner wrote:
>> - default etag hash algo for dynamic response bodies has changed to
>> sha1 from crc32 and cannot be changed through an INI setting
>>
>> etags on dynamic content are, well, subject to change anyway,
>> so I don't see major troubles
>
> I presume that a calculated etag value can be returned as an
> alternative. Something dictated by the service using this facility?
> There is provision for the etag value being a version number or some
> similarly defined value.
>
Definitely:
http://devel-m6w6.rhcloud.com/mdref/http/Env/Response/setEtag
--
Regards,
Mike