segunda-feira, 28 de maio de 2012 04:16I want to set the default version of my storage service so that it recognizes range headers using the format "bytes=nnn-". The only documentation I can find for setting the service properties is to use the REST API. Is there really no way to do this through the portal? It seems like overkill to get a remote management tool set up just to set one parameter.
Todas as Respostas
segunda-feira, 28 de maio de 2012 09:15Moderador
Do you mean something like this? x-ms-version: 2011-10-01 in the HttpRequest header?
As far as i know, there's no related function in Management portal, because Azure platform is a public cloud platform, everyone can send request to Azure if they can provide credentials (such as certificate of REST API). correct me if i am wrong.
segunda-feira, 28 de maio de 2012 16:55
Yes, like that, but apparently you can set the default value for the version using the management API:
I can set this up, but it seems really shortsighted to not be able to set and view these values in the management portal.
terça-feira, 29 de maio de 2012 02:41Moderador
As far as i know, Microsoft Storage Service Version can not be set a default value, x-ms-version property is Required for all authenticated requests. Specifies the version of the operation to use for this request. It's not just a property of Storage service, you can also looks other REST APIs, every REST APIs requires this version number.
In general, the latest version number is recommended, more details please refer to the following article:
Hope this helps.
terça-feira, 29 de maio de 2012 04:27
The above link would suggest you are incorrect, you can set a "DefaultServiceVersion" in the Blob Service Properties using the management API.
I prefer to avoid implementation-specific headers as much as possible, especially in a case like this where I'm using the Range header in a way that's defined in the HTTP 1.1 protocol spec:
I'm writing a client library to manage progressive download of content--it may be hosted by Azure or somewhere else. I expect every server to properly implement the HTTP protocol and I don't want to shoehorn implementation hacks just to get Azure to behave properly.
terça-feira, 29 de maio de 2012 07:07Moderador
I suggest you post your idea on this site:
Hope this helps.
- Marcado como Resposta Arwind - MSFTModerator segunda-feira, 4 de junho de 2012 09:10