0005250: %u fails to populate user principal in access log

Viewing Issue Simple Details [ Jump to Notes ]

[ View Advanced ] [ Issue History ] [ Print ]

Category

Severity

Reproducibility

Date Submitted

Last Update

0005250

[Resin]

minor

always

10-19-12 07:58

10-22-12 16:23

Reporter

cowan

View Status

public

Assigned To

ferg

Priority

normal

Resolution

fixed

Status

closed

Product Version

Summary

0005250: %u fails to populate user principal in access log

Description

From W. Tao

Our access log format settings:

<access-log path="/var/log/resin4/access.log"
format='"%{host}i" %h %l %u %t "%r" %s %b "%{Referer}i" "%{User-Agent}i" %T'
rollover-size="500mb"/>

Log entry from access.log

Oct 19 16:22:52 xxx xxx - - [19/Oct/2012:16:22:50 +1100] "GET /xxx.js HTTP/1.1" 200 415 "https://xxx" [^] "Mozilla/5.0 (Windows NT 5.1) AppleWebKit/537.4 (KHTML, like Gecko) Chrome/22.0.1229.94 Safari/537.4" 0

you can see that no username was logged although the servlet request has principle already.

Additional Information

I verified we are setting LOGIN_USER (caucho.user) in the session, but not LOGIN_USER_NAME (caucho.user.name). HttpServetRequestImpl.getRemoteUser(boolean) queries for LOGIN_USER_NAME which is not set.

Attached Files

Relationships

Notes
(0006065) ferg 10-22-12 16:23	server/02ep

Issue History
Date Modified	Username	Field	Change
10-19-12 07:58	cowan	New Issue
10-22-12 16:23	ferg	Note Added: 0006065
10-22-12 16:23	ferg	Assigned To	=> ferg
10-22-12 16:23	ferg	Status	new => closed
10-22-12 16:23	ferg	Resolution	open => fixed
10-22-12 16:23	ferg	Fixed in Version	=> 4.0.33

Mantis 1.0.0rc3[^]

29 total queries executed.
26 unique queries executed.