Score:0

Did/When did the Apache Custom Log Format of SSL env vars change?

mx flag

For years I have been accessing SSL custom log variables using directives like

CustomLog /var/log/apache2/ssl_type_log "%t %h %{SSL_PROTOCOL}x %{SSL_CIPHER}x "%r" %b"

Specifically: %{SSL_CIPHER}x

Today, apache was killed and restarted. I think I got a version updated to 2.4.52 in the process, but I'm not sure what version I was upgrading from. But suddenly it didn't like the %{SSL_CIPHER}x format. I eventually found that %{SSL_CIPHER}e doesn't make it error; but nor does it work.

https://httpd.apache.org/docs/2.4/mod/mod_ssl.html#logformats specifically says %{SSL_CIPHER}x. https://httpd.apache.org/docs/2.4/mod/mod_log_config.html#formats says %{...}e for env vars. And I got it working against by setting SSLOptions +StdEnvVars as you'd expect.

But why does %{...}x throw a configuration error suddenly, especially when it used to work fine and it seems to still be correct usage per documentation?

Gerard H. Pille avatar
in flag
Could it be Apache has trouble with the quotes on the CustomLog line?
mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.