azure-storage-files

Uploading a file in Azure File Storage using node.js

不想你离开。 提交于 2019-12-05 13:20:41
问题 We are trying create an webservice to upload files to Azure file storage using node.js service. Below is the node.js server code. exports.post = function(request, response){ var shareName = request.headers.sharename; var dirPath = request.headers.directorypath; var fileName = request.headers.filename; var body; var length; request.on("data", function(chunk){ body += chunk; console.log("Get data"); }); request.on("end", function(){ try{ console.log("end"); var data = body; length = data.length

Uploading a file in Azure File Storage using node.js

烈酒焚心 提交于 2019-12-03 22:44:21
We are trying create an webservice to upload files to Azure file storage using node.js service. Below is the node.js server code. exports.post = function(request, response){ var shareName = request.headers.sharename; var dirPath = request.headers.directorypath; var fileName = request.headers.filename; var body; var length; request.on("data", function(chunk){ body += chunk; console.log("Get data"); }); request.on("end", function(){ try{ console.log("end"); var data = body; length = data.length; console.log(body); // This giving the result as undefined console.log(length); fileService

Azure File Storage URL in browser showing InvalidHeaderValue

坚强是说给别人听的谎言 提交于 2019-12-01 02:16:01
I am trying to access the URL given in Azure for a file on the Azure File Storage format, however I am getting this error below. Is it possible to get this? Why would they offer a public URL when it's useless? Also how can I access this directly from IIS? <Error> <Code>InvalidHeaderValue</Code> <Message> The value for one of the HTTP headers is not in the correct format. RequestId:5d681103-0a1a-00cc-5555-5s4849000000 Time:2016-02-04T14:06:50.1786949Z </Message> <HeaderName>x-ms-version</HeaderName> <HeaderValue/> </Error> K232 Gaurav already mentioned a similar question here where it says you

Azure File Storage URL in browser showing InvalidHeaderValue

岁酱吖の 提交于 2019-11-30 21:41:19
问题 I am trying to access the URL given in Azure for a file on the Azure File Storage format, however I am getting this error below. Is it possible to get this? Why would they offer a public URL when it's useless? Also how can I access this directly from IIS? <Error> <Code>InvalidHeaderValue</Code> <Message> The value for one of the HTTP headers is not in the correct format. RequestId:5d681103-0a1a-00cc-5555-5s4849000000 Time:2016-02-04T14:06:50.1786949Z </Message> <HeaderName>x-ms-version<

Download an excel file and read content with azure functions

一笑奈何 提交于 2019-11-29 14:44:51
问题 I am trying to write a C# Azure Function to download and open an excel file using the OpenXml-SDK. Office Interop doesn't work here because office is not available to the Azure Function. I am trying to use OpenXml-SDK to open and read the file which seems to require a path to the saved file and not the url or a Stream downloaded from the remote url. Given I don't know of a way to temporary store the excel file in Azure Functions, I used Azure File Storage. I uploaded the excel file from the

Azure Files - System error 53

我怕爱的太早我们不能终老 提交于 2019-11-29 09:36:08
I am trying to use Azure Files and I am getting the following System error 53. Any ideas? There are two possible reasons for getting this error if you are trying to mount your Azure file shares from outside of Azure Datacenter via SMB 3.0. Your client OS needs support SMB 3.0, for example use Windows 8, Windows 10, Windows Server 2012. The port 445 (TCP Outbound) needs to be opened by your ISP or firewall. The SMB protocol is dependent on this port if you mount from outside of Azure Datacenter, and I do notice some ISP blocked this port (e.g. Comcast). You can refer to the links below to do a

Azure Files - System error 53

只愿长相守 提交于 2019-11-28 02:57:39
问题 I am trying to use Azure Files and I am getting the following System error 53. Any ideas? 回答1: There are two possible reasons for getting this error if you are trying to mount your Azure file shares from outside of Azure Datacenter via SMB 3.0. Your client OS needs support SMB 3.0, for example use Windows 8, Windows 10, Windows Server 2012. The port 445 (TCP Outbound) needs to be opened by your ISP or firewall. The SMB protocol is dependent on this port if you mount from outside of Azure