On 04.11.2016 16:05, Ewald Dieterich wrote:
This leads to a segfault in mod_session.c, session_identity_decode() because the tokenization assumes valid data when in this case it's just binary rubbish (one of the apr_strtok() calls segfaults).
BTW, the segfault in mod_session.c, session_identity_decode() happens when the session data (z->encoded) starts with this string: =&
