New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The URL of one blob snapshot shows incorrectly #2788
Comments
The url is the url returned by the api. We won't fix it on our side. |
I confirm that this is true. Not only the copy to URL button is gone but you can find it by right click on the file but it does give a local URL instead of the usable URL. |
@egdedudette Thanks for raising this up. We will re-triage this issue. |
Why was this closed? |
Because the last time we triage this issue, we found that "the url is the url returned by the api" and this issue is raised by our tester. We usually don't process data directly from the server unless there is an explicit need. |
There is a need because We use it to test files and now we can't. Big problem for us. |
This was created by the new update. |
Are you saying that this was working in a previous version? If so, can you share the version number that this was working in? Also, can you share examples of the URLs you are receiving from the previous version and the new version? We want to make sure we're understanding your problem so we know what exactly needs to be fixed. |
OK. I am able to copy the URL on my office compute with CRD. It works there. version 1.12.0 Azure 10.3.3 |
@egdedudette The %2F characters are the URL encoding for "/". CRD? User name? You mean something like https://user@host.com? You don't have to share the exact URLs. You can edit the endpoints and filenames to something more generic. Just enough that we can get a sense of the URL form you're getting and the form you're expecting. |
https://curriculumtesting.blob.core.windows.net/files/FolderName%2Fnameoffnextfolderr%2Findex.html Actually I just noticed it is in 2 places. After the folder name and between the file name. So basicall folder names are followed with these characters %2F instead of a slash. and before the slash was not encoded. (I verified with the URL from older version). |
@egdedudette I think that's by design. The encoding is used to differentiate slashes used in the URL path from slashes used to delimit folder names. Do you know if your blob container is HNS enabled? |
Well this is so annoying. Before I could just copy the URL and now I have to remove the undesirable characters and replace them! SERIOUSLY! Great improvement!!!! |
How do you check HNS enabled? |
Next to your storage account node we show (ADLS Gen2) if the storage account is HNS enabled. To summarize your concern, you would like to have the copy url give a url that contains the |
@egdedudette The encoded slashes should have no impact on whether they work or. The blob service should know how to handle them. Hierarchical namespace (HNS) is enabled when you create the storage account containing the blob container. You can tell if the account has HNS enabled if the storage account node as "(ADLS Gen2)" next to the name, like this: |
if says (Key) and we have not changed anything and it was working before as I mentioned. So obviously something is different and it is the encoding of the /. |
@egdedudette OK, I copied a URL that has the %2F in it, but it seems to work just fine on our end. Don't worry, we'll get to the bottom of this! To do that, we'll need your help in figuring out exactly what you're doing to see what we may be doing wrong on our end. Once we can figure out how the problem occurs, we can figure out how to fix it. First, the "(Key)" part tells me that this is a storage account you connected to manually using an account name and key. In other words, you did not need to sign in using an Azure account. Does that sound correct? Second, I assume you're using the Copy URL menu command, yes? Or are you clicking on Properties? Third, can you share with me the exact steps you take from starting up Storage Explorer all the way up to the point you are getting your URL? Here are the steps I am taking, so let me know if I did something different than what you did.
At this point, I am able to see my picture in my browser. I would expect the URL to work, because my container has "blob" public read access. If my container's public read access is "off", then I get this error page, as I would expect:
Do my steps follow yours accurately, or did I do something majorly different than you? |
First, the "(Key)" part tells me that this is a storage account you connected to manually using an account name and key. In other words, you did not need to sign in using an Azure account. Does that sound correct? OK. I just noticed in the property window that it says: I did exactly as you told me and I get the same result with the pasted / as %2F and my browser cannot read it properly. |
@egdedudette I don't think that's a URL problem then, if your browser loads still loads the file, albeit with some bugs. I don't know a lot about Animate, but if you're creating HTML files, can you download the file and check the HTML to see if it looks correct? You should be able to open the original and downloaded files in your browser to check if they both perform the same way. Usually you just need a URL that looks like this: file:///C:/path/to/your/file.html (if you're on Windows, and your file is on the C drive). |
But the same file runs properly with the previous version of Azure. |
Files copied are the index.html of published Animate CC media recap: AZURE PREVIOUS VERSION
AZURE CURRENT VERSION
Note: the file loads but fails as it seems to not read the html properly to get the media ID number which does not even makes senses since it reads it when the / is used. |
@egdedudette Just to confirm I'm understanding you correctly:
What we can do from this pointAssuming the above is all correct, I think we have enough information to dig deeper on our end. Since this is a different problem than the original issue posted above, I've created issue #2939 to track your problem going forward. We will report our findings and progress there. Feel free to share any additional information you have through the new issue. What can you do now?Since this was working for you in earlier versions, go ahead and downgrade to the previous version. You can download 1.12.0 by clicking on this link. |
yes, exactly. If after placing the / it works as expected or as in previous version. |
and thank you for looking into it. |
Verified on build 20200514.2. This issue has been fixed. So close it. |
This issue reproduce on build master/20200529.3. So we re-open it. |
Verified on build 20200602.3. This issue has been fixed. So close it. |
Storage Explorer Version: 1.13.0
Build: 20200403.15
Branch: rel/1.13.0
Platform/OS: Windows 10/ Linux Ubuntu 16.04/ macOS High Sierra
Architecture: ia32/x64
Regression From: Not a regression
Steps to reproduce:
Expect Experience:
The URL shows correctly.
Actual Experience:
The URL shows incorrectly.
More Info:
The text was updated successfully, but these errors were encountered: