i do soemthing like this to get as much info as possible:
Enumeration headerNames = request.getHeaderNames();
while(headerNames.hasMoreElements())
{
String headerName = (String)headerNames.nextElement();
String headerText = (String)request.getHeader(headerName));
// then print it or append it to an email mesg.
}
you can take a similar approach with request.getAttributeNames() and
request.getParameterNames()
Joe Niski | Senior Software Engineer/Internet Architect
Nine Dots
503.548.2176
Portland . Irvine . San Francisco . Toronto
[EMAIL PROTECTED]
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, July 31, 2001 3:47 PM
> To: JRun-Talk
> Subject: Gleaning original URI in errorPage
>
>
>
> Hello,
>
> I'm creating an error page that I hope will provide me
> with some useful debugging information. I refer to the error
> page from a variety of .jsp files using the directive:
>
> <%@ page errorPage="error.jsp" %>
>
> In the error.jsp file, I'd like to be able to figure out
> what file caused the error in the first place. However, the
> command, "request.getRequestURI()" merely returns "/error.jsp"
> Does anyone have any thoughts as to how I might get the referring
> page? The stack trace of the exception does show me what Java
> file threw the exception, but I'd like to be able to display
> something like the original URI.
>
> Thanks,
> Sam Greenfield
> Senior System Engineer
> Sports Illustrated
>
>
>
> Archives: http://www.mail-archive.com/[email protected]/
> Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Structure your ColdFusion code with Fusebox. Get the official book at
http://www.fusionauthority.com/bkinfo.cfm
Archives: http://www.mail-archive.com/[email protected]/
Unsubscribe: http://www.houseoffusion.com/index.cfm?sidebar=lists
