Skip to content
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

Testcase error: The file's contents show incorrectly after copying the URL into a browser #1233

Closed
v-xinda opened this issue Mar 2, 2021 · 1 comment
Labels
Milestone

Comments

@v-xinda
Copy link

v-xinda commented Mar 2, 2021

OS: All
Build Version: v0.15.0-alpha3

Repro Steps:

  1. Create a new template file with following contents --> Save it as child.json.
{
	"$schema": "https://schema.management.azure.com/schemas/2019-04-01/deploymentTemplate.json#",
	"contentVersion": "1.0.0.0",
	"parameters": {
	"parameter1": {
	"type": "string",
	"metadata": {
	"description": "description"
	}
	},
	"parameter2": {
	"type": "int",
	"metadata": {
	"description": "description"
	}
	}
	},
	"functions": [],
	"variables": {
	"v1": "[parameters('unknown-parameter')]"
	},
	"resources": [],
	"outputs": {}
	}
  1. Create a new storage account --> Create a new blob container.
  2. Upload the child.json file to the blob --> Right-click on the uploaded file and Choose "Copy URL".
  3. Copy this URL into a browser --> Enter.
  4. Check whether the file's contents show correctly in the browser or not.

Expect:
The file's contents show correctly in the browser.

Actual:
The file's contents show incorrectly in the browser
image

@v-xinda v-xinda added the AT-CTI label Mar 2, 2021
@MarcusFelling MarcusFelling added this to the 0.15.1 milestone Mar 8, 2021
@StephenWeatherford StephenWeatherford changed the title The file's contents show incorrectly after copying the URL into a browser Testcase error: The file's contents show incorrectly after copying the URL into a browser Mar 11, 2021
@StephenWeatherford
Copy link
Contributor

This was an error in the testcase. I've updated it.

Note however the following known issue that occurs with some SAS tokens and not others:

#1281

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants