Leon,
Thank you for the test - but I still get a null user-agent right after the
login. Here is a snippet of my code:
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"
"http://www.w3.org/TR/html4/loose.dtd";>
<%@ include file="/common/taglibs.jspf"%>
<%@ page import="com.ltoj.common.Constants" %>
<html:html locale="true">
<head>
<%@ include file="/common/meta.jspf" %>
<title><decorator:title/></title>
<script type="text/javascript" src="<c:url
value='/scripts/environment.js'/>"></script>
<script type="text/javascript" src="<c:url
value='/scripts/util.js'/>"></script>
<script type="text/javascript" src="<c:url
value='/scripts/helptip.js'/>"></script>
<script type="text/javascript" src="<c:url
value='/scripts/tabs.js'/>"></script>
<script type="text/javascript" src="<c:url
value='/scripts/CalendarPopup.js'/>"></script>
<script type="text/javascript" src="<c:url
value='/scripts/chartWizard.js'/>"></script>
<link rel="stylesheet" type="text/css" media="all" href="<c:url
value='/styles/default.css'/>" />
<link rel="stylesheet" type="text/css" media="all" href="<c:url
value='/styles/messages.css'/>" />
<link rel="stylesheet" type="text/css" media="all" href="<c:url
value='/styles/tabs.css'/>" />
<decorator:head/>
<%
String _userAgent = request.getHeader("user-agent");
out.write("USER-AGENT='"+_userAgent+"'");
...
Here's the sequence:
1) I issue a request to this page.
2) CMA says "oh, that's protected" and shows my custom login page. I get
user-agent displayed fine:
USER-AGENT='Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.12)
Gecko/20050915 Firefox/1.0.7'
3) But on the next page (the original target page of the request),
user-agent shows as null.
USER-AGENT='null'
I can refresh the page or go to any other page in my application and the
user agent is fine again.
The only thing a bit non-standard about this JSP page is that it is a
SiteMesh decorator page.
If I run the same test, same pages in Tomcat 5.5.9 I never get user-agent of
null.
Our application does check the user-agent header a good bit. We use Select
lists with option groups - but some browsers do not support this so we
simulate it by indenting the select options ourselves.
Luckily all of this activity happens well after the initial login - so we
are safe, now that I changed the decorator to make sure user-agent is not
null before doing anything with it.
But it seems other applications might be affected by this - no?
Thanks again - Richard
-----Original Message-----
From: Leon Rosenberg [mailto:[EMAIL PROTECTED]
Sent: Sunday, October 09, 2005 1:45 PM
To: Tomcat Users List; [EMAIL PROTECTED]
Subject: Re: Tomcat 5.5.12 and user-agent header
Hmm, I downloaded 5.5.12 and tried the agent-header specific code with it:
public void processLogin(User user, HttpServletRequest req,
HttpServletResponse res) {
StringBuffer info = new StringBuffer();
info.append("login ");
info.append(user.getUserName());
info.append(" [");
info.append(user.getUserId().getPlainPresentation());
info.append("] ");
info.append(user.getEmail());
info.append(" ");
info.append(UserHelper.getGenderDescription(user.getGender()));
info.append(" ");
info.append(UserHelper.getStatusDescription(user.getMembershipStatus()));
info.append(" ");
info.append(req.getRemoteAddr());
info.append(" / ");
info.append(req.getRemoteHost());
info.append(" Agent: ");
info.append(req.getHeader("user-agent"));
log.info(info);
}
outcome was:
2005-10-08 15:36:50,453 INFO - login leon [6] [EMAIL PROTECTED] male premium
127.0.0.1 / 127.0.0.1 Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US;
rv:1.7) Gecko/20040626 Firefox/0.8
which I think was same behaviour as before.
I took tomcat out of the box (5.5.12 tar.gz) and only changed the http port.
regards
leon
On 10/8/05, Richard Mixon <[EMAIL PROTECTED]> wrote:
> I am just using the standard HTTP connector. This is on my development
> workstation so I don't normally run JK and Apache, except for final
testing.
>
> On the developer list I did see one mention of user-agent header, but
> on closer inspection it appeared to be for a completely different issue.
>
> Thanks - Richard
>
> -----Original Message-----
> From: news [mailto:[EMAIL PROTECTED] On Behalf Of Bill Barker
> Sent: Friday, October 07, 2005 10:13 PM
> To: tomcat-user@jakarta.apache.org
> Subject: Re: Tomcat 5.5.12 and user-agent header
>
>
> "Richard Mixon" <[EMAIL PROTECTED]> wrote in message
> news:[EMAIL PROTECTED]
> >I tested out my application on 5.5.12 yesterday and noticed one small
> >anomally. I had a JSP in my sitemesh decorator "default.jsp" that
> >ends up wrapping the login page for container managed
> >authentication. This page had a statement
> > String _userAgent =
> >request.getHeader("user-agent").toLowerCase();
> >
> > It gets a null-pointer exception in 5.5.12, but under 5.5.9 it runs
fine.
> > In
> > 5.5.12, after the login succeeds then the user-agent headers appear
> > to be there just fine, but not on the initial login page.
> >
> > Is this a known issue?
> >
>
> It's certainly not a known issue. It would help a lot if you could
> tell us which Connector you are using at the time (e.g. HTTP/1.1,
> HTTP/1.1-APR, AJP/1.3, AJP/1.3-APR).
>
> > Thank you - Richard
> >
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
