Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision Both sides next revision
litespeed_wiki:lslb:zconf [2018/04/19 13:38]
Ron Saad [API Configuration Messages]
litespeed_wiki:lslb:zconf [2018/04/19 13:40]
Ron Saad [Sending ZeroConfig API Messages]
Line 14: Line 14:
 curl --silent -X POST --data-binary $DATA https://<​i>​user:​password</​i>​@<​i>​my_load_balancer.com:​my_listner_port</​i>/<​i>​API_COMMAND</​i>?​name=<​i>​my_cluster</​i>​ curl --silent -X POST --data-binary $DATA https://<​i>​user:​password</​i>​@<​i>​my_load_balancer.com:​my_listner_port</​i>/<​i>​API_COMMAND</​i>?​name=<​i>​my_cluster</​i>​
 </​pre>​ </​pre>​
-<​p><​b>​The fields <​i>​user</​i>​ and <​i>​my_cluster</​i>​ must NOT contain ':'​ (colon) characters.</​html>​+<​p><​b>​The fields <​i>​user</​i>​ and <​i>​my_cluster</​i>​ must NOT contain ':'​ (colon) characters.</b></​html>​
 ==== Handling ZeroConfig API Responses ==== ==== Handling ZeroConfig API Responses ====
 Messages to the ZeroConfig API receive HTTP responses, with common status codes (typically 200 for success, 400 for invalid messages / failures). Response bodies may contain data from the ZeroConfig system or error messages detailing a problem encountered while trying to process a received message. Messages to the ZeroConfig API receive HTTP responses, with common status codes (typically 200 for success, 400 for invalid messages / failures). Response bodies may contain data from the ZeroConfig system or error messages detailing a problem encountered while trying to process a received message.
  • Admin
  • Last modified: 2020/11/18 15:36
  • by Lisa Clarke