`@Y~a1e.x}6D .UuE#0t*vd1̅%l6GdL'JbיfO |9RٖaZamu>}˻ןMUhj+p)"-ܷ=8{GŭMJNnRƖV\BܔY' -nXT#Uٕ%sZ)c"Gwx6+ Aj*[^e#YJ-;aj47K ɫ3N+t%8A]hSm 8h,(rPOݮ|V8A;:}dd.(;-˓"6Q89ŷ5"-k2a01VOS0i$Հ3[<-[;`]ؙ}CګuCszNT 9 8-eCi̤30iZAW2M>BЯzb|_iyk4 >p(+J7Hp=2J8 zV>_W=sUzj!!xüd&"c $bEI ^%yBWf-jjLvxua6NOfF9>tZ__0B1:x_%פ6OԄ$ &y<]Zh u3e]޳i~o4j*kx)XKo;4++oZぜ#>%A/o`Jeo;/VퟜflM0a[-%8U 65pc!Y.0ҮhQhCx4}Y_uc54?P&t]X1/+eGQy߷Q,\zR0lvMNC  Ya_e_ L"Yz y]rκA,JBU E2Iz:,nTO`2{r!`M]啃ٱA)8Dv3%əb%.3&NJ3UŔm3)YK[q="Oq\z "au֩×`WR2xgB0چ HDG ٹ&㝉0Qd7Vx]ʁaU/jHBf24M@W)꫱BNtC(k$9}\r$OƲFhɒZb V/EF(d!"c|UĵgPyBVZ3D\4d]"[ZOD#7SeDE~kI/X%iAكv$vHR}2<&W ;M_}46凘4\ {|qu@J 3ry4ߑZEdJl~TJ^aɪi^džМ6[ g&GD+*> \aъn懹NQ ^}<c]EI=r;s4ݝH@ZO1澺ro!ư=STEw }aq_dġrYɯM1lD˓7B@]Wv7/Ur(*`N1U*-D*^K,7Vx1zdpo$2hCI%>d〩x!rg֤s3)s)L{4/)$  *wdh@,z.s6ʳ*3URҫ_ĿOgGx'O >בP0"ȿ3b]p)'92X\z.DF X9ےF'I0<]B7msbo5\Ӄ\€al%mq#0^F+l^{0^JKя=`>Eutr2 >]PS Ez[6Xip@kґӇDFb!%~b?0xyC:Wv/W+NAQ,* x[zqwԄ>/$(LW@hcP[2T'fHXK+8!rӞik6 Ьv L]f΂4˴bPK'^D(6~$#oUq@)2]R7̮d!g3}pU`H}$}GFR[~6)mA?h X^|KXb˹췡_$T[:\zqL Log message after request to /foo/* is processed: 
<Location "/foo/">
  LogMessage "/foo/ has been requested"
</Location>
  • Log message if request to /foo/* is processed in a sub-request: 
    <Location "/foo/">
  LogMessage "subrequest to /foo/" hook=type_checker "expr=-T %{IS_SUBREQ}"
</Location>
    The default log_transaction hook is not executed for sub-requests, therefore we have to use a different hook.
  • Log message if an IPv6 client causes a request timeout: 
    LogMessage "IPv6 timeout from %{REMOTE_ADDR}" "expr=-T %{IPV6} && %{REQUEST_STATUS} = 408"
    Note the placing of the double quotes for the expr= argument.
  • Log the value of the "X-Foo" request environment variable in each stage of the request: 
    <Location "/">
  LogMessage "%{reqenv:X-Foo}" hook=all
</Location>
    Together with microsecond time stamps in the error log, hook=all also lets you determine the times spent in the different parts of the request processing.
    • top

    LogMessage Directive

    Description:Log user-defined message to error log
    Syntax:LogMessage message [hook=hook] [expr=expression]
    Default:Unset
    Context:directory
    Status:Experimental
    Module:mod_log_debug

    This directive causes a user defined message to be logged to the error log. The message can use variables and functions from the ap_expr syntax. References to HTTP headers will not cause header names to be added to the Vary header. The messages are logged at loglevel info.

    The hook specifies before which phase of request processing the message will be logged. The following hooks are supported:

    Name
    pre_translate_name
    translate_name
    type_checker
    quick_handler
    map_to_storage
    check_access
    check_access_ex
    insert_filter
    check_authn
    check_authz
    fixups
    handler
    log_transaction

    The default is log_transaction. The special value all is also supported, causing a message to be logged at each phase. Not all hooks are executed for every request.

    The optional expression allows to restrict the message if a condition is met. The details of the expression syntax are described in the ap_expr documentation. References to HTTP headers will not cause the header names to be added to the Vary header.

    Available Languages:  en  |  fr 

    top

    Comments

    Notice:
    This is not a Q&A section. Comments placed here should be pointed towards suggestions on improving the documentation or server, and may be removed by our moderators if they are either implemented or considered invalid/off-topic. Questions on how to manage the Apache HTTP Server should be directed at either our IRC channel, #httpd, on Libera.chat, or sent to our mailing lists.