InvalidHeaderValue x-ms-version 2020-04-08
See original GitHub issue- @azure/storage-file-datalake:
- 12.3.0:
Describe the bug When we try to interact with a Data Lake Gen2 Storage Account where HNS is enabled we receive the error. The same function is working fine with a Storage account where HNS is disabled. When we revert to version 12.0.0 the same function (e.g.: DataLakeFileSysteClient.exists()) is working.
To Reproduce
getClient() {
if (!this.client) {
this.client = new DataLakeServiceClient(
https://${this.accountName}.dfs.core.windows.net
,
this.credentials
);
}
return this.client;
}
let fileSystem = this.getClient().getFileSystemClient(this.fileSystemName); let exists = await fileSystem.exists();
Issue Analytics
- State:
- Created 3 years ago
- Comments:11 (6 by maintainers)
Top Results From Across the Web
Azure File Storage URL in browser showing InvalidHeaderValue
The error you received indicates that you are missing x-ms-version header. But once you set it, you will receive another error if you...
Read more >Versioning for the Azure Storage services | Microsoft Learn
If a request has a valid x-ms-version header, the storage service uses the specified version. All requests to the Table and Queue services...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
@nulltoken It should be working now. Could you retry?
@nulltoken The server hit is not rolled-out with the right configuration. Already notified the service team to fix it.