Directing to Index.html
Novell Cool Solutions: Question & Answer
Reader Rating 
Q:
AS wrote: I have an accelerator set up for eGuide that seems to be functioning properly with one exception. When I browse to http://eguide.xxx/eGuide I would expect iChain to pick up the index.html page and redirect me to /eGuide/servlet/eGuide, instead I get a page not found error. If I browse directly to http://eguide.xxx/eGuide/servlet/eGuide it works fine. This is a public resource so no authentication is required. If I bypass iChain (go straight to Tomcat) I do get redirected from the /eGuide to /eGuide/servlet/eGuide which leads me to believe that this is an iChain issue.
A:
Try going to http://eguide.xxx/eGuide/ (i.e. with a trailing slash) and see if that works - it should.The actual request you are making is for a file called eGuide (with no extension) at the document root. Web servers often have to deal with this and so are usually prepared to assume you meant a directory and so redirect your browser to the root of the indicated directory (/eGuide/). The web server is then usually configured not to give a directory listing and instead passes back a index.html or other default file. My guess is that the index.html file has some sort of refresh directive to redirect the browser to eGuide/servlet/eGuide.
I think your problem is that your PR definition does not actually cover the request you make. Either train users to add the trailing slash or change your PR to http://eguide.xxx/eGuide* (i.e. remove the /).
Novell Cool Solutions (corporate web communities) are produced by WebWise Solutions. www.webwiseone.com