fix: remove middleware preventing range requests

Author: Alan Shaw

src/index.js

@@ -17,7 +17,6 @@ import {
 } from '@web3-storage/gateway-lib/handlers'
 import {
   withContentClaimsDagula,
-  withHttpRangeUnsupported,
   withVersionHeader,
   withCarBlockHandler
 } from './middleware.js'
@@ -45,7 +44,6 @@ export default {
       withCarBlockHandler,
       withContentClaimsDagula,
       withFormatRawHandler,
-      withHttpRangeUnsupported,
       withFormatCarHandler,
       withContentDispositionHeader,
       withFixedLengthStream

src/middleware.js

@@ -15,22 +15,6 @@ import { handleCarBlock } from './handlers/car-block.js'
  * @typedef {import('@web3-storage/gateway-lib').UnixfsContext} UnixfsContext
  */
 
-/**
- * Validates the request does not contain a HTTP `Range` header.
- * Returns 501 Not Implemented in case it has.
- * @type {import('@web3-storage/gateway-lib').Middleware<import('@web3-storage/gateway-lib').Context>}
- */
-export function withHttpRangeUnsupported (handler) {
-  return (request, env, ctx) => {
-    // Range request https://github.com/web3-storage/gateway-lib/issues/12
-    if (request.headers.get('range')) {
-      throw new HttpError('Not Implemented', { status: 501 })
-    }
-
-    return handler(request, env, ctx)
-  }
-}
-
 /**
  * Middleware that will serve CAR files if a CAR codec is found in the path
  * CID. If the CID is not a CAR CID it delegates to the next middleware.