Even if `unique_id` and `s->unique_id` are identical it is a bit odd to
`isttest()` `unique_id` and then use `s->unique_id` in the call to `http_add_header()`.
This "issue" was introduced in
a17e66289c08a5bfadc1bb5b5f2c618c9299fe1b,
because before that commit the function returned the length of the ID, as it
was not an ist.
/* send unique ID if a "unique-id-header" is defined */
if (isttest(sess->fe->header_unique_id) &&
- unlikely(!http_add_header(htx, sess->fe->header_unique_id, s->unique_id)))
+ unlikely(!http_add_header(htx, sess->fe->header_unique_id, unique_id)))
goto return_int_err;
}
/* Generates a unique ID based on the given <format>, stores it in the given <strm> and
* returns the unique ID.
-
+ *
* If this function fails to allocate memory IST_NULL is returned.
*
* If an ID is already stored within the stream nothing happens existing unique ID is