BlobNotFound when using syncCopyFromURL

Utkarsh 1

Hello,
I am using @azure/storage-blob npm and am trying to figure out a way to add an image directly from url to blob. What I came up with was :

const blobService4 = new BlockBlobClient(
      process.env.AZURE_CONNECTION_STRING,
      containerName,
      blobName,
    );

let a = await blockBlobClient.syncCopyFromURL(url)
return a

What this did for me was save it inside the container, but the url was not public or what, I am not quite sure , but i wasn't able to access the image. What I want is to store the image to the container and display it as the products image. What I get is BlobNotFound Error. Can any one tell me what I am doing wrong ?

2 answers

deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-10-19T15:49:11.64+00:00

@Utkarsh
If you wish to make blobs public you need to change the access level on the container. Once this is set any new blob uploaded to the containers should be public.

Please update the setting and let me know if resolves your issue.

------------------

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Utkarsh 1 Reputation point

2020-10-20T05:33:27.627+00:00

Does this access level looks fine, because the images are not working on this new container in the image, and that was the first thing i looked into when uploading the image with the code. I only get this problem when I am trying to upload a pic directly from a url using syncCopyFromURL instead of upoadStream. Everything works fine when i use the uploadStream function and i can view the image, which is not the case in the when i use syncCopyFromURL which throw blobNotFound error

deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-10-20T18:13:25.76+00:00

@Utkarsh When using syncCopyFromURL is the blob being uploaded? You should be able to see the blob inside the container. You have Public access level set to blob, so any blob in the container should be publicly available.

Utkarsh 1 Reputation point

2020-10-21T04:37:28.003+00:00

Blob is being uploaded and it was inside the container. I don't quite understand your statement "You have Public access level set to blob, so any blob in the container should be publicly available." but the access level of the container is public so not quite sure what you mean there.

deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-10-21T16:50:50.093+00:00

@Utkarsh I was referring to Public read access for blobs only: Blobs within the container can be read by anonymous request, but container data is not available anonymously. Anonymous clients cannot enumerate the blobs within the container. If this is set you should be able to directly access the blob. Please go to properties and copy the url for one of the blobs uploaded to see if it can be accessed. One other thing to check is to make sure Allow Blob public access is enabled for the storage account. This can be found under Configuration for the storage account.

Utkarsh 1 Reputation point

2020-10-22T04:14:47.867+00:00

I checked it, and it was enabled, so that's not the issue, the issue is somewhat specific to the blob when uploading it. Only while using the syncCopyFromURL function of the @azure/storage-blob npm. Because uploadStream function is working fine, and I can access the images while using uploadStream, but yeah I can't view them, they get downloaded whenever I click to open the image.

deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-10-22T17:45:22.087+00:00

@Utkarsh So to clarify the images are available in the container and can be downloaded when accessing the blob URL directly? If so then it does not appear to be a permissions issue. Perhaps when using syncCopyFromURL the content-type is not being set as an image. Can you verify if you are seeing any difference in the blob properties? Compare a blob that was copied vs one that was uploaded.

Utkarsh 1 Reputation point

2020-10-23T05:14:01.377+00:00

this is the image that was uploaded via upload stream

this is the image uploaded via syncCopyFromUrl
Sign in to comment
deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-10-23T17:01:48.9+00:00

@Utkarsh The difference is that the blob that used syncCopyFromURL has a content type of application/octet-stream. There was a similar thread here. Try to see if you can modify the content type to image/jpeg using blobHTTPHeaders.

Hope this helps! Let me know if it does not resolve your issue.

-------------------------------

Please don’t forget to "Accept the answer" and “up-vote” wherever the information provided helps you, this can be beneficial to other community members.
Please sign in to rate this answer.
Utkarsh 1 Reputation point

2020-11-02T07:31:32.983+00:00

Sorry for the late reply to this was caught up in other changes. What sync copy from url does is set the content type to image/jpeg or whatever the extension of the image is and application/octet-stream is set when i try uploading it via upload stream function of the @azure/storage-blob npm. I think a better documentation of all the function of "@azure/storage-blob" npm would help people out, like uploading directly from url and uploading a file using upload stream. Also those images which are saved as octet-stream download whenever I open the link, but the image never opens when I try opening the image that is saved as image/jpeg. Let me know if I need to be more clear. I can explain this in two case scenario if you want

deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-11-03T18:24:48.237+00:00

When the content-type of the blob is set to image/jpeg and you open the link in your browser it should display in your browser rather than downloading. If content-type is set to something else, in this case, application/octet-stream, the browser will download the file. If you are saying the image is not being opened and cannot be downloaded then something else might be going wrong. Can you give me more details about how you are accessing the image? If you have a test url I can work with that might also be helpful.

Utkarsh 1 Reputation point

2020-11-10T12:48:00.26+00:00

That part is done I don't have any issue with image/jpeg part, but when I use the syncCopyFromURL function, it does copy the image but it does not make the image public for some reason. And only with synccopy from url

const blobService4 = new BlockBlobClient(
process.env.AZURE_CONNECTION_STRING,
containerName,
blobName,
// options
);
let a = await blobService4.syncCopyFromURL(url)

That is the code I am having issue with.

deherman-MSFT 34,841 Reputation points Microsoft Employee

2020-11-10T21:39:42.49+00:00

Going back I noticed your copy source appears to not be a blob. I am wondering if this might be the issue. The REST API specifies that the source should be a blob. I recommend posting this over to the github issues page. The experts over there should be able to get this sorted. Apologies I haven't been able to solve the issue. Once you have an issue posted please link it here so I can make sure this gets handled.
Sign in to comment

Share via

BlobNotFound when using syncCopyFromURL

2 answers