ShallowEtagHeaderFilter supports the
header, so it would make sense if it would also support the
header as well. This would make the out of the box behaviour of this filter much more in sync with the HTTP spec (which is the whole point of the filter).
The same shallow implementation would be fine here as well, same as now.