I need to ensure that relevant inforamtion and no sensitive data is being dumped in DEA by tomcat's access logs. However, I nothing is being written to the access logs. I checked this path:
/var/vcap/data/warden/depot/<warden_handle_id>/tmp/rootfs/home/vcap/app/.java-buildpack/tomcat/logs
My valve configuration in server.xml is:
`
<Service name='Catalina'>
<Connector port='${http.port}' bindOnInit="false" proxyPort="443" scheme="https" secure="true"/>
<Engine defaultHost='localhost' name='Catalina'>
<Valve className='org.apache.catalina.valves.RemoteIpValve' protocolHeader='x-forwarded-proto'/>
<Valve className='com.gopivotal.cloudfoundry.tomcat.logging.access.CloudFoundryAccessLoggingValve'
pattern='[ACCESS] %{org.apache.catalina.AccessLog.RemoteAddr}r %l %t %D %F %B %S vcap_request_id:%{X-Vcap-Request-Id}i'
enabled='${access.logging.enabled}'/>
<Host name='localhost'
failCtxIfServletStartFails='true'>
<Listener className='com.gopivotal.cloudfoundry.tomcat.lifecycle.ApplicationStartupFailureDetectingLifecycleListener'/>
</Host>
</Engine>
</Service>
`
Buildpack version: 3.17
Please let me know if there is any configuration miss or if more info is required on this. Thanks in advance.
I need to ensure that relevant inforamtion and no sensitive data is being dumped in DEA by tomcat's access logs. However, I nothing is being written to the access logs. I checked this path:
/var/vcap/data/warden/depot/<warden_handle_id>/tmp/rootfs/home/vcap/app/.java-buildpack/tomcat/logs
My valve configuration in server.xml is:
`