You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@infra.apache.org by "Henri Yandell (JIRA)" <ji...@apache.org> on 2009/12/26 09:02:29 UTC
[jira] Created: (INFRA-2404) Turn off access logging
Turn off access logging
-----------------------
Key: INFRA-2404
URL: https://issues.apache.org/jira/browse/INFRA-2404
Project: Infrastructure
Issue Type: Task
Security Level: public (Regular issues)
Components: JIRA
Reporter: Henri Yandell
No need for JIRA to do access logging - the httpd is already taking care of that.
It's a useful debug tool to make sure calls are hitting from mod_jk, but not needed all the time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (INFRA-2404) Turn off access logging
Posted by "Jeff Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12795571#action_12795571 ]
Jeff Turner commented on INFRA-2404:
------------------------------------
I'll turn them off so they stop cluttering the logs. JIRA 4.0's log4j config stores them in a separate (rotated) log file. I think we should keep them then, as JIRA's access logs lists the JIRA user performing the action, which httpd doesn't, and so preserves a record of who did what.
> Turn off access logging
> -----------------------
>
> Key: INFRA-2404
> URL: https://issues.apache.org/jira/browse/INFRA-2404
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Henri Yandell
> Assignee: Jeff Turner
>
> No need for JIRA to do access logging - the httpd is already taking care of that.
> It's a useful debug tool to make sure calls are hitting from mod_jk, but not needed all the time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Assigned: (INFRA-2404) Turn off access logging
Posted by "Jeff Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Turner reassigned INFRA-2404:
----------------------------------
Assignee: Jeff Turner
> Turn off access logging
> -----------------------
>
> Key: INFRA-2404
> URL: https://issues.apache.org/jira/browse/INFRA-2404
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Henri Yandell
> Assignee: Jeff Turner
>
> No need for JIRA to do access logging - the httpd is already taking care of that.
> It's a useful debug tool to make sure calls are hitting from mod_jk, but not needed all the time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (INFRA-2404) Turn off access logging
Posted by "Jeff Turner (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/INFRA-2404?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jeff Turner resolved INFRA-2404.
--------------------------------
Resolution: Fixed
> Turn off access logging
> -----------------------
>
> Key: INFRA-2404
> URL: https://issues.apache.org/jira/browse/INFRA-2404
> Project: Infrastructure
> Issue Type: Task
> Security Level: public(Regular issues)
> Components: JIRA
> Reporter: Henri Yandell
> Assignee: Jeff Turner
>
> No need for JIRA to do access logging - the httpd is already taking care of that.
> It's a useful debug tool to make sure calls are hitting from mod_jk, but not needed all the time.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.