Is your servlet container listening directly to port 80?
Yes. It's pure tomcat - not behind Apache Webserver.
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
On Sun, May 9, 2010 at 5:47 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:
Is your servlet container listening directly to port 80?
Yes. It's pure tomcat - not behind Apache Webserver.
If not, do the forwarding via a proxy on whatever you are using
as a frontend. In that frontend,
I don't think ProxyPass will work (at least it didn't used to) if you
try to use the / path, so that might be the trouble you're seeing
(if you're seeing any).
On Sun, May 9, 2010 at 6:47 PM, Chris Colman
chr...@stepaheadsoftware.com wrote:
Is your servlet container listening directly to port 80?
Using the word 'context' was probably misleading on my part. In servlet
containers context=app. What I was talking about was the first 'path'
element after the domain name,
Eg., content in www.mysite.com/content
In this case I'm talking about a single app but I set up multiple
different URL
Should still work. If you're using the filter, the idea is that it will
only respond to the URLs that it recognizes, and will pass other requests
down the chain.
--
Jeremy Thomerson
http://www.wickettraining.com
On Sun, May 9, 2010 at 8:48 PM, Chris Colman
chr...@stepaheadsoftware.comwrote:
Oh, of course! Sorry I was mistakenly assuming we'd use /* which would
match everything but if we use the non wild card / then that will only
do an exact match and other URLs with /content etc., will still be able
to match their own separate patterns and redirect to their appropriate
you would use /*, wicket lets urls that it cannot map fallthrough and
be handled as usual.
additionally wicketfilter has some context params that lets you
specify ignore masks, see the source/javadocs.
-igor
On Sun, May 9, 2010 at 8:22 PM, Chris Colman
chr...@stepaheadsoftware.com wrote:
Oh,
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
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.comwrote:
I was just wondering if there has been any
