It would be beneficial to add a configuration option to disable DNS resolution
of the requestor IP.
This would be useful for performance tuning. Also for deployments where an
intermediate reverse proxy/access gateway masks the real requestor IP (and
x-forwarded-for isn't used)
What steps will reproduce the problem?
1. Attempt to access PWM from a host with an IP that the PWM server cannot
resolve to a DNS name.
2. Observe a significant delay in establishing a session with (in our
deployment this was between 10-15 seconds)
What is the expected output? What do you see instead?
1. No delay in establishing a session & no hostname resolution in the logging.
What version of the product are you using? On what operating system?
PWM 1.5.2, Windows 2003 Server, Java 1.6, Tomcat 6
Please provide any additional information below.
The DNS resolution is currently implemented in SessionFilter.java
// mark the user's hostname in the session bean
ssBean.setSrcHostname(readUserHostname(req, pwmSession));
Original issue reported on code.google.com by oner...@gmail.com on 4 Feb 2011 at 10:04
Original issue reported on code.google.com by
oner...@gmail.com
on 4 Feb 2011 at 10:04