You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Understandably, it will only try to look up MIME type when options.headers is set, so for my above code to work, I would include a headers: {} in the options argument.
My question is, I'm not sure why it only tries to detect when options.headers is set. I, for one, would not want to do any thing with the request headers, yet still want the MIME to be look up immediately.
Would changing to the below in core.js:addFile cause any problem?
Hi,
Currently I have a request stream and I pass that stream to node-cloudfiles'
addFile
ascloudfile.addFile("container", "{remote: "fileName.ext", stream: readStream}, callback)
However, since the request stream has
content-type
set toapplication/octet-stream
, it is saved asapplication/octet-stream
in Rackspace.From
core.js:addFile
:Understandably, it will only try to look up MIME type when
options.headers
is set, so for my above code to work, I would include aheaders: {}
in theoptions
argument.My question is, I'm not sure why it only tries to detect when
options.headers
is set. I, for one, would not want to do any thing with the request headers, yet still want the MIME to be look up immediately.Would changing to the below in
core.js:addFile
cause any problem?The text was updated successfully, but these errors were encountered: