The payload pattern can be customized in order to change the way the payload
ends. In order to end a payload with something else than an empty line, a
-customized pattern can be set between '<<' and '\n'. Only 7 characters can be
-used in addition to '<<', otherwise this won't be considered a payload.
-For example, to use a PEM file that contains empty lines and comments:
+customized pattern can be set between '<<' and '\n'. Up to 64 characters can be
+used in addition to '<<', otherwise this won't be considered a payload. It
+should be enough to use random payload patterns. For example, to use a PEM file
+that contains empty lines and comments:
# echo -e "set ssl cert common.pem <<%EOF%\n$(cat common.pem)\n%EOF%\n" | \
socat /var/run/haproxy.stat -
int pcli_next_pid; /* next target PID to use for the CLI proxy */
int pcli_flags; /* flags for CLI proxy */
- char pcli_payload_pat[8]; /* payload pattern for the CLI proxy */
+ char pcli_payload_pat[65]; /* payload pattern for the CLI proxy, including trailing \0 */
struct ist unique_id; /* custom unique ID */
#include <haproxy/tools.h>
#include <haproxy/version.h>
-#define MAX_PAYLOAD_PATTERN_SIZE 7
+#define MAX_PAYLOAD_PATTERN_SIZE 64
#define PAYLOAD_PATTERN "<<"
static struct applet cli_applet;