Updated VES publishAnyEvent HTTP Headers requirement to VES 7.1.1

Includes a change in HTTP headers required in publishAnyEvent use-case.
Authorization header "Required?" property set to "No" to align with publishEventBatch, and VES7.1.1 implementation.

Signed-off-by: deen1985 <damian.nowak@nokia.com>
Change-Id: Id7fc8bbc0b62044a2cf8524ca2bd8029763283ce
Issue-ID: VNFRQTS-863

diff --git a/docs/Chapter8/ves7_1spec.rst b/docs/Chapter8/ves7_1spec.rst
index 2427c6f..44b3725 100644 (file)
--- a/docs/Chapter8/ves7_1spec.rst
+++ b/docs/Chapter8/ves7_1spec.rst
@@ -3729,7 +3729,7 @@ case-insensitive):
 |               |          |          |                                       |
 |               |          |          | -  application/json                   |
 +---------------+----------+----------+---------------------------------------+
-| Authorization | string   | Yes      | The username and password are formed  |
+| Authorization | string   | No       | The username and password are formed  |
 |               |          |          | into one string as                    |
 |               |          |          | ``username:password``. This string is |
 |               |          |          | then Base64 encoded to produce the    |