api-guidelines

api-guidelines copied to clipboard

Azure Guidelines - Update ETag & Optimistic Concurrency section

3

If you choose to use a Weak ETag, then...

markweitzel

Adding descriptions for x-ms-*-request-id headers

4

...intended usage and descriptions.

johanste

JeffreyRichter

JeffreyRichter

Add guidelines about durations using a time unit (seconds, minutes, etc.) with a number value and NOT using ISO8601

1

JeffreyRichter

Add guidance on the format for time duration values

1

In particular, don't use the ISO 8601 duration format because it is poorly supported in language runtimes. We should have guidance something like: > Consider not using ISO8601 durations in...

mikekistler

Ayse1974

Improve guidance on date-time values passed in headers

4

The current Azure API Guidelines state (though maybe not clearly) that date-time values passed in headers should be formatted as RFC 1123 date-time strings. And certain headers. such as "Date"...

mikekistler

Is it intended that the two guidelines spell this differently?

bexxx

mikekistler