Navigation Menu

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

Adding URI with trailing space should remove space or fail #1387

Closed
FaronFaulk opened this issue May 22, 2019 · 1 comment
Closed

Adding URI with trailing space should remove space or fail #1387

FaronFaulk opened this issue May 22, 2019 · 1 comment
Assignees
Labels
🪲 bug Issue is not intended behavior ❔ investigate We need to look into this further 😤 easy ✅ merged A fix for this issue has been merged
Milestone

Comments

@FaronFaulk
Copy link

Storage Explorer Version: 1.8
Platform/OS: Windows 10
Architecture: x64
Regression From: _Was this working in a previous version? not that i know of.

Bug description
Creating a new connection that contains a connection string with a trailing space allows the connection to be created (no error), but then fails when you try to use it.

Steps to Reproduce

  1. Click 'Connect to Azure Storage'
  2. select 'Use a connection string'
  3. Click Next
  4. Paste the connection string that contains a trailing space.
  5. Click Next.
  6. Click Connect. Connection is created successfully.
  7. Click the Blob Storage under the new connectoid
  8. observe the error:
    "[Window Title]
    Microsoft Azure Storage Explorer

[Content]
The provided URI "core.windows.net " is invalid.

[OK]"

Expected Experience
If the connection string contains a trailing space, ASE should either remove it automagically (since it's never valid) or prompt the user to remove it.
ASE should NEVER continue without error if the connection string is invalid.

Actual Experience
image

Additional Context
Add any other context about the problem here, such as unusual system configurations, network restrictions, etc.

@craxal craxal added 🪲 bug Issue is not intended behavior ❔ investigate We need to look into this further 😤 easy labels Jun 24, 2019
@craxal craxal added this to the 1.10.0 milestone Jun 24, 2019
@JasonYeMSFT JasonYeMSFT self-assigned this Jun 24, 2019
@JasonYeMSFT JasonYeMSFT added the ✅ merged A fix for this issue has been merged label Jun 25, 2019
@JasonYeMSFT
Copy link
Contributor

Close as fixed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🪲 bug Issue is not intended behavior ❔ investigate We need to look into this further 😤 easy ✅ merged A fix for this issue has been merged
Projects
None yet
Development

No branches or pull requests

3 participants