Use case — logout of session

Logout of REST session.

WorkStation# curl --noproxy 10.100.167.104 --cookie
 "sessionId=09CG1bRuT5hkCPzI97mmDjpn4uLtsmgkBsAaWUr9h7GxlkbsiASak1PEyj7Ov3n" -X 
DELETE http://10.100.167.104:80/rest/v1/login-sessions

The switch will respond with a message simular to: 204 No Content.

[root@UbuntuServer5224 ~]# curl --noproxy 192.168.1.1 -v --cookie "sessionId=8XU2msUzBJbXYClpFyVmaageB4iiRE6C94QSvYIfd3xiHelPjgUraYOx5JjWIUq" -X DELETE http://192.168.1.1:80/rest/v1/login-sessions
* About to connect() to 192.168.1.1 port 80 (#0)
*   Trying 192.168.1.1... connected
> DELETE /rest/v1/login-sessions HTTP/1.1
> User-Agent: curl/7.22.0 (x86_64-pc-linux-gnu) libcurl/7.22.0 OpenSSL/1.0.1 zlib/1.2.3.4 libidn/1.23 librtmp/2.3
> Host: 192.168.1.1
> Accept: */*
> Cookie: sessionId=8XU2msUzBJbXYClpFyVmaageB4iiRE6C94QSvYIfd3xiHelPjgUraYOx5JjWIUq
>
< HTTP/1.1 204 No Content
< Server: eHTTP v2.0
< Connection: keep-alive
< RequestId:
<
* Connection #0 to host 192.168.1.1 left intact
* Closing connection #0
[root@UbuntuServer5224 ~]#