I added AccessLogValve in server.xml and was able to find the exact problem.
The problem is not with "/", the problem is following:

1. When I load the screen initially, it loads fine, its able to find all
the components.
2. When I click on save, it calls following servlet
10.16.10.90 - - [06/Jun/2012:13:41:55 -0400] "POST /uom/servlet/uom.update
HTTP/1.1" 302 -
3. After save loads again (it displays the saved data after clicking on
save in the same JSP), it calls components like this:
10.16.10.90 - - [06/Jun/2012:13:41:55 -0400] "GET
/uom/*action*/images/hsnlogo.gif
HTTP/1.1" 400 1109
10.16.10.90 - - [06/Jun/2012:13:41:55 -0400] "GET
/uom/*action*/images/logout.gif
HTTP/1.1" 400 1106
10.16.10.90 - - [06/Jun/2012:13:41:56 -0400] "GET
/uom/*action*/images/pixel_trans.gif
HTTP/1.1" 400 1121

It is adding 'action' in the URL and I have no clue where it is coming
from.




On Wed, Jun 6, 2012 at 7:38 AM, Konstantin Kolinko
<knst.koli...@gmail.com>wrote:

> 2012/6/6 Dharamshila Khandelwal <dharmshil...@gmail.com>:
> > Tim,
> >
> > It worked fine with IE 6.
> > Tomcat logs clearly say that the path is invalid.
> > Wierd this is that when the screen is loaded for the first time, it works
> > fine. If I click on save (which makes a call to servlet) , it starts
> giving
> > invalid path error.
> > I know that its not a tomcat issue, but is there any configuration I need
> > to change to make sure that the paths are always taken relative to base
> > context?
> >
>
> 1. What is that "save" that you click on?
> calls a servlet using relative path.
> 2. What exactly Tomcat version you are using?
> 6.0.32
> 3. Configure an AccessLogValve inside the <Host> element in server.xml
> and use a custom pattern in it to log "Referer" request header.
>
> That is to log what requests are actually coming to Tomcat and from what
> pages.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org
> For additional commands, e-mail: users-h...@tomcat.apache.org
>
>

Reply via email to