Bug 983858 - [GSS] (6.3.x) access-log does not log 404 for non-existent context when enable-welcome-root is set to false in EAP 6
Summary: [GSS] (6.3.x) access-log does not log 404 for non-existent context when enabl...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise Application Platform 6
Classification: JBoss
Component: Web
Version: 6.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: Rémy Maucherat
QA Contact: Radim Hatlapatka
URL:
Whiteboard:
Depends On: 1125934
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-07-12 06:28 UTC by Masafumi Miura
Modified: 2018-12-02 17:13 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 1125934 (view as bug list)
Environment:
Last Closed: 2014-10-06 13:46:51 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Masafumi Miura 2013-07-12 06:28:02 UTC
Description of problem:

access-log setting does not log 404 for non-existent context when enable-welcome-root is set to false in EAP 6


Steps to Reproduce:

1. Configure web subsysmte to set enable-welcome-root to "false" and enable access-log. For example:

        <subsystem xmlns="urn:jboss:domain:web:1.4" default-virtual-server="default-host" native="false">
            <connector name="http" protocol="HTTP/1.1" scheme="http" socket-binding="http"/>
            <virtual-server name="default-host" enable-welcome-root="false">
                <alias name="localhost"/>
                <alias name="example.com"/>
                <access-log/>
            </virtual-server>
        </subsystem>

2. Access non-existent context and get 404 like:

    curl -v http://localhost:8080/foobar

3. Check the access log


Actual results:

Nothing is logged in the access logging.


Expected results:

404 should be logged in the access logging.

Comment 1 Radim Hatlapatka 2014-08-01 11:26:49 UTC
The issue still valid in latest build EAP 6.3.0.ER10.

Comment 10 Jimmy Wilson 2014-09-30 08:17:19 UTC
@Mark: Yes, we can drop this from 6.3.z.


Note You need to log in before you can comment on or make changes to this bug.