Yes, as newly introduced RequestStrategy does not have this method anymore, and I did not want to leave RequestProcessors (those deprecated ones) still littered here.

Also, as I checked, no implementation of RequestProcessor was doing anything else with this method, they never returned `false` here.

Finally, even if they _would return false_ here, I am completely sure it would just cause problems, similar to https://github.com/sonatype/nexus/pull/820 HTTP connection leak, as the RRS items (those wrapping HTTP response body) would bubble up all way to the REST layer, where in case of a `?describe` requests -- and sure for any non-200 OK response too -- ContentLocators are just tossed away ( = leak same as NEXUS-5468 in fixed in pull above).