> Why should it redirect to /foo/xyz.abc?
Because I've entered /foo/ and a typical plain-html-webserver redirects
to /foo/index.html.
Thats not true many serve you the index.html on that dir but in the url you mostly just see /
At least for homepages this is mostly the case.
> What kind of resource is not found?
> Can you give an example?
I've tried to sketch that in my original posting. Sorry, if it wasn't
clear enough. I'll try with different wordings:
I enter the URL http://localhost:8080/foo/ in the browser. My Index.html
(and the page content ariving my browser) contains a graphic reference
to "graphics/logo.png" (it is found and displayed correctly when I enter
the URL http://localhost:8080/foo/graphics/logo.png). Since the
wicket-servlet obviously is redirecting to
http://localhost:8080/foo?page=0 , the browser obviously expects the
graphic to be at http://localhost:8080/graphics/logo.png (note the
missing "/foo" after the port!).
so you just want to mix wicket pages and resources in the root of youre webapplication?
Or are you also serving index.html (a plain resource) in the /foo/ dir what is mapped as the wicket servlet url?
That shouldn't be done.
What does that index.html do?? Move it to the real root of youre webapplication.
/foo is there for dynamic pages.
johan
