Fix forwarding the content-length header which was screwing up HTTP2 requests in Chrome

Author: billiegoose

README.md

@@ -3,7 +3,7 @@ When you need a file, but the headers ain't good, who you gonna call? CORS Buste
 
 ## What is this?
 
-This is the software running on https://cors-buster.now.sh, a free
+This is the software running on https://cors-buster-tbgktfqyku.now.sh, a free
 service for AJAX users struggling to work around the fact that many websites
 do not implement CORS headers, even for static content.
 
@@ -21,7 +21,7 @@ Uncaught (in promise) TypeError: Failed to fetch
 You can do this instead, and now there's no error:
 
 ```
-window.fetch('http://cors-buster.now.sh/nodejs.org/dist/v6.10.2/node-v6.10.2-linux-x64.tar.gz')
+window.fetch('https://cors-buster-tbgktfqyku.now.sh/nodejs.org/dist/v6.10.2/node-v6.10.2-linux-x64.tar.gz')
 ```
 
 ## Is this safe?

index.js

@@ -106,6 +106,7 @@ async function service (req, res) {
     }
   )
   for (let h of exposeHeaders) {
+    if (h === 'content-length') continue
     if (f.headers.has(h)) {
       res.setHeader(h, f.headers.get(h))
     }

package.json

@@ -1,6 +1,6 @@
 {
   "name": "cors-buster",
-  "version": "2.0.0",
+  "version": "2.0.1",
   "description": "When you need a file, but the headers ain't good, who you gonna call? CORS Buster!",
   "main": "index.js",
   "scripts": {