2.8.3

Merge pull request #89 from wmhilton/patch-1
Allow setting User-Agent Header
2018-06-01 17:52:26 -07:00 · 2018-06-01 17:33:29 -07:00 · 2018-06-01 16:47:30 -04:00 · 2018-05-09 19:26:31 -07:00
3 changed files with 3 additions and 4 deletions
@@ -323,6 +323,5 @@ var unsafeHeaders = [
 	'trailer',
 	'transfer-encoding',
 	'upgrade',
-	'user-agent',
 	'via'
 ]
@@ -1,6 +1,6 @@
 {
  "name": "stream-http",
-  "version": "2.8.1",
+  "version": "2.8.3",
  "lockfileVersion": 1,
  "requires": true,
  "dependencies": {
@@ -1,6 +1,6 @@
 {
  "name": "stream-http",
-  "version": "2.8.1",
+  "version": "2.8.3",
  "description": "Streaming http in the browser",
  "main": "index.js",
  "repository": {
@@ -10,7 +10,7 @@
  "scripts": {
    "test": "npm run test-node && ([ -n \"${TRAVIS_PULL_REQUEST}\" -a \"${TRAVIS_PULL_REQUEST}\" != 'false' ] || npm run test-browser)",
    "test-node": "tape test/node/*.js",
-    "test-browser": "DEBUG=airtap airtap --loopback airtap.local -- test/browser/*.js",
+    "test-browser": "airtap --loopback airtap.local -- test/browser/*.js",
    "test-browser-local": "airtap --no-instrument --local 8080 -- test/browser/*.js"
  },
  "author": "John Hiesey",
Author	SHA1	Message	Date
John Hiesey	65aed45b2d	2.8.3	2018-06-01 17:52:26 -07:00
John Hiesey	05dd964945	Merge pull request #89 from wmhilton/patch-1 Allow setting User-Agent Header	2018-06-01 17:33:29 -07:00
William Hilton	4f73bb1a3c	Allow setting User-Agent Header The User-Agent header has not been forbidden since Firefox 43 (see https://developer.mozilla.org/en-US/docs/Glossary/Forbidden_header_name). > Note: The User-Agent header is no longer forbidden, as per spec — see forbidden header name list (this was implemented in Firefox 43) — it can now be set in a Fetch Headers object, or via XHR setRequestHeader(). I've had success setting it in Firefox and Edge for `fetch` and it should work for XMLHttpRequest as well but I'm too lazy to look up how to use XMLHttpRequest. I haven't had any luck setting User-Agent it in Chrome yet - may be a Chrome bug - but I'm not seeing any warnings in the terminal when I use it either, so I don't think allowing it will cause any spurious warnings.	2018-06-01 16:47:30 -04:00
John Hiesey	663f88323c	2.8.2	2018-05-09 19:26:31 -07:00