Sorry I need some more help, have one more weird issue at my plate now,

I am using base tag and pulling out the webapplication context path to it like this so that all links in the page becomes relative to this path,i am doing something like below,

<base href="${pageContext.request.contextPath}">

which resolves to " /mydomain"/ in IE and base tag looks like this <base href="/mydomain"/> in IE and in other browers like ff/chrome/opera/safari it resolves to "/mydomain" and base tag here looks like <base href="/ourstory">

however all links resolves perfectly fine in IE and when I click on any link, it opens perfectly fine with path http://localhost:8080/mydomain/link1.jsp but the same link when checked via other browser like FF/Opera/chrome/safari it says page not found and gives me 404 error.The same link path now looks like http://localhost:8080/link1.jsp in those browsers.

what is that i am doing wrong here ?


On 12/30/2011 9:06 PM, Hassan Schroeder wrote:
On Thu, Dec 29, 2011 at 7:15 PM, Kiran Badi<ki...@poonam.org>  wrote:

One final doubt can I have one servlet similar to listener which will listen
to the clicks, store the path info,validate the sessions and then push that
data to some jsp and I can include that jsp in my all pages.Do I need to
implement this exactly the way we implement httpsession listener ?
I'm not sure what you mean by "listen to the clicks", but you have no
way to know (other than JavaScript/AJAX) what the client is doing;
the simplest approach to this problem is to use a Filter to push each
request (or component, e.g. pathInfo) into an Array stored in session.

Then yes, you can format and expose the data via a page fragment
and/or a custom tag.



---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
For additional commands, e-mail: users-h...@tomcat.apache.org

Reply via email to