[jboss-jira] [JBoss JIRA] (WFLY-5353) Unable to set resolve-hosts for access-log
Radim Hatlapatka (JIRA)
issues at jboss.org
Thu Sep 17 02:48:00 EDT 2015
[ https://issues.jboss.org/browse/WFLY-5353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13109737#comment-13109737 ]
Radim Hatlapatka commented on WFLY-5353:
----------------------------------------
I agree with you and believe that setting it on the connector should be enough.
> Unable to set resolve-hosts for access-log
> ------------------------------------------
>
> Key: WFLY-5353
> URL: https://issues.jboss.org/browse/WFLY-5353
> Project: WildFly
> Issue Type: Bug
> Components: Web (Undertow)
> Affects Versions: 10.0.0.Beta2
> Reporter: Radim Hatlapatka
> Assignee: Stuart Douglas
> Priority: Critical
>
> In previous versions of EAP (Web subsystem) there was possible to enable resolving hosts for access logging. This is not possible to enable with Undertow.
> Steps for enabling in JBoss Web:
> This was accomplished by setting {{resolve-hosts}} attribute of access-log to {{true}} ({{/subsystem=web/virtual-server=default-host/configuration=access-log:add(resolve-hosts=true)}}) and enabling lookups for connector ({{/subsystem=web/connector=http:write-attribute(name=enable-lookups, value=true)}}).
> In Undertow subsystem there is only possible to enable resolving peer address ({{/subsystem=undertow/server=default-server/http-listener=default:write-attribute(name=resolve-peer-address, value=true)}}), which doesn't have by itself any impact on output in access-log
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
More information about the jboss-jira
mailing list