JonasWells-2782 avatar image
0 Votes"
JonasWells-2782 asked JonasWells-2782 commented

Microsoft Azure BLOB Storage - Ignition Project

Hello all,

I am attempting to use the Ignition platform to access Azure BLOB Storage. Within Ignition, there exists a Python2.7 (Jython specifically) scripting functionality that is being used to construct the PUT and GET requests to the BLOB storage. I am unable to use the Azure.Blob.Storage methods provided by Microsoft as they have dependencies on C.

Recently, I have been able to upload and download images from the Server using a REST API approach. The issue that is arising however is that the required 'Content-Length' header is troublesome to compute dynamically. That is, when providing the byte length of the file to upload, it does not match the length interpreted by the Server. Perhaps I am misunderstanding how this number is calculated, but the documentation provided indicates that the byte length is the 'Content-Length'. Has anybody encountered something similar to this?

Note: The mismatched 'Content-Lengths' cause the request to fail and the difference between them is not small enough for a simple calculation error (I think).


· 3
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@JonasWells-2782 Firstly, apologies for the delay in responding here and any inconvenience this issue may have caused.
For better understanding the issue: Can you please share the more information on this issue (code, error message screenshot)?
Are you referring to any article?

0 Votes 0 ·

@JonasWells-2782 Just checking in to see if you have had a chance to see the previous response. Could you share the above required information to understand/investigate this issue further?

0 Votes 0 ·

Hello Sumarigo,

I received some additional information through Ignition. It appears the platform I am using is encoding some of the data on its own. This ultimately results in Microsoft Blob Storage interpreting the data to have a different length than what I had anticipated. I am currently working through a way to avoid this encoding (or finding what the length of the encoded data will be). I will update here. I appreciate your help.


0 Votes 0 ·

0 Answers