Skip to content

"parse error" when log format is NCSA extended/combined #2

@weppos

Description

@weppos

Posted on behalf of toro.

when log format is NCSA extended/combined, %u ( the userid of the person requesting the document) always causes the parse error.

I think that the cause of the problem is here.
http://code.simonecarletti.com/repositories/entry/apachelogregex/lib/apache_log_regex.rb#L167

Not

when element == ‘%U’

but

when element == ‘%u’

I might be wrong… but after I change it , no error .
thanks.

via http://www.simonecarletti.com/blog/2009/02/apache-log-regex-a-lightweight-ruby-apache-log-parser/#comment-6964

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions