> Hi, > > Le 10/09/2014 15:54, [email protected] a ?crit : >>> You can use the log-format directive below, in your frontend, to log >>> SSL >> related informations: >>> log-format %ci:%cp\ [%t]\ %ft\ %b/%s\ %Tq/%Tw/%Tc/%Tr/%Tt\ %ST\ %B\ >>> %CC\ %CS\ %tsc\ %ac/%fc/%bc/%sc/%rc\ %sq/%bq\ %hr\ %hs\ >>> {%sslv/%sslc/%[ssl_fc_sni]/%[ssl_fc_session_id]}\ >>> "%[capture.req.method]\ %[capture.req.hdr(0)]%[capture.req.uri]\ >>> HTTP/1.1" >>> >>> then try to anonymize logs and post some lines in attachment. >>> >>> Baptiste >>> >> >> I have included part of the log using two different ciphers. I see some >> strange symbols in ssl session id, with both ciphers. > > Please use %[ssl_fc_session_id,hex] instead of %[ssl_fc_session_id], > this will convert the binary value to hexadecimal (the change appeared > with 1.5-dev23). > > -- > Cyril Bont? >
Ok i can see it now, thanks. I will try to find out when is my django app actually using ssl_fc_session_id, but I haven't understood after all how is an empty ssl_fc_session_id related to haproxy low performance? Evie
