.abort: Don't set headers to default #128
Open
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
In
.abort()
, we were settingheaders
todefaultHeaders
. This causes a couple problems.First, this means you can't set the full
User-Agent
. Since.open()
callsthis.abort()
,User-Agent
will be set after the consumer callsxhr.open(...)
. If the consumer then callsxhr.setRequestHeader("User-Agent", "foo");
, the actualUser-Agent
would end up asnode-XMLHttpRequest, foo
instead of justfoo
becausesetRequestHeader()
appends to the existing value (set by.abort()
) if it already exists.The
test-headers.js
test actually setsuser-agent
tonode-XMLHttpRequest-test
and validates this, but it only works because it setsuser-agent
and notUser-Agent
. Since.abort()
was just callingheaders = defaultHeaders
without settingheadersCase
as well, the test headers ended up as:Which would send
node-XMLHttpRequest-test
over the wire since it was last.To solve this, I think we can simply not set
headers = {}
in.abort()
, as.send()
will set the default headers later anyways.