website: clarify uuid format (#5014)
This commit is contained in:
parent
c8965c840d
commit
5f55d8809b
|
@ -269,3 +269,12 @@ to allow clients to know if address translation is in effect, the
|
||||||
`X-Consul-Translate-Addresses` header will be added if translation is enabled,
|
`X-Consul-Translate-Addresses` header will be added if translation is enabled,
|
||||||
and will have a value of `true`. If translation is not enabled then this header
|
and will have a value of `true`. If translation is not enabled then this header
|
||||||
will not be present.
|
will not be present.
|
||||||
|
|
||||||
|
## UUID Format
|
||||||
|
|
||||||
|
UUID-format identifiers generated by the Consul API use the
|
||||||
|
[hashicorp/go-uuid](https://github.com/hashicorp/go-uuid) library.
|
||||||
|
|
||||||
|
These UUID-format strings are generated using high quality, purely random bytes.
|
||||||
|
It is not intended to be RFC compliant, merely to use a well-understood string
|
||||||
|
representation of a 128-bit value.
|
||||||
|
|
Loading…
Reference in New Issue