Depends on if the range header fix is in the replica still or not.
If not the the solution is still to run your own proxy ie. prptl.io
The simplest solution is skip certification entirely for that path if you are fine with that risk.
A more complex solution is to certify but don’t include the request range header in the certification, this is less risky than skipping certification entirely but not without any risk at all. A malicious replica could return the ranges out of order for example.
There’s no way to do this in a fully certifiable manner right now.
@skilesare what solution do you use on your own proxy?
We just served everything as raw but without raw. 
We were adding in certification and got v1 working about the time you all released 2, and then we were waiting on NatLabs1 to finish the v2 stuff and never got around to it.
We basically had forked the old icx proxy and were being less restrictive with headers and letting range requests go through.
1 Like