Is your servlet container listening directly to port 80? If not, do the forwarding via a proxy on whatever you are using as a frontend. In that frontend, have it rewrite the URLs (i.e. mod_proxy and mod_rewrite).
Otherwise, can you have your app mounted on "/"? -- Jeremy Thomerson http://www.wickettraining.com On Sat, May 8, 2010 at 12:40 AM, Chris Colman <chr...@stepaheadsoftware.com>wrote: > I'll explain the problem in detail. I think it's similar to the link I > provided but maybe not: > > I have a site whose home page that is rendered via: > > www.mysite.com/content/home/pName/pValue > > but obviously the users will get their via: > > www.mysite.com > > I want the home page to be serviced via a forward to > www.mysite.com/content/home/pName/pValue > > so that the search engines don't have to experience a 301 redirect. > (where pName/pValue are required parameters that can be passed to any > page) > > I forward via: > > RequestDispatcher rd = servletContext. > > getRequestDispatcher("www.mysite.com/content/home/pName/pValue"); > rd.forward(req, res); > > I don't mind if all subsequent pages a user visits use the full form of > the URL and these full URLs appear in the browser address bar. Eg., > > www.mysite.com/content/contactUs/pName/pValue > > www.mysite.com/content/products/pName/pValue > > www.mysite.com/content/home/pName/pValue > > The forward works fine but any links on that page don't work because the > context of the wicket web app is 'content' - a separate servlet is used > to 'catch' URL's of the form www.mysite.com and redirects to the wicket > app. > > All my BookmarkablePageLinks are constructed assuming the 'content' > context. I can change that so they work from www.mysite.com but then > when the pages with www.mysite.com/content/blah... are visited those > same links do not work. > > >-----Original Message----- > >From: Jeremy Thomerson [mailto:jer...@wickettraining.com] > >Sent: Saturday, 8 May 2010 10:53 AM > >To: users@wicket.apache.org > >Subject: Re: Any solution for the context problem with the relative > links > >of BookmarkablePageLink? > > > >That wasn't a problem - it was someone configuring the proxy > incorrectly. > > What (specifically) are you encountering? > > > >-- > >Jeremy Thomerson > >http://www.wickettraining.com > > > > > > > >On Fri, May 7, 2010 at 7:44 PM, Chris Colman > ><chr...@stepaheadsoftware.com>wrote: > > > >> I was just wondering if there has been any developments on the > problem > >> outlined in this post because I'm having the same problem but wanted > to > >> avoid the Index link solution: > >> > >> > http://apache-wicket.1842946.n4.nabble.com/BookmarkablePageLink-relative > >> -path-Dilemma-td1933044.html > >> > >> --------------------------------------------------------------------- > >> To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > >> For additional commands, e-mail: users-h...@wicket.apache.org > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > >
