Again, not a Jetty user. But sensing your exasperation, I'll throw out some theories and stuff.
I guessing these xml files you're configuring have to do with domains, not host names. That may be why your host based entries like "www.domain" entries are not doing squat there. Perhaps there's a different file or config method to handle the host name part of a Jetty setup, or you may just want to put a 301 redirect into your Jetty setup for each domain for now. The Jetty web server would tell any client requesting the "www.domain" resources that they have permanently moved to the "domain" address. A 302 will tell them the move is temporary. Using a 302, you can still try to fix it later. With a 301, your sites won't need or use the "www" anymore. It seems like more enterprises are dumping the "www" lately, although I'm not an expert on the wisdom of doing it. A Google of "Jetty 301 redirect" produces the method(s) to do this, like http://markmail.org/message/h76w57eumpg5ucoy?q=Jetty+301+redirect&page=1&refer=evagvohsr3e4h4su Looks like a handler called "MovedContextHandler" will do it. This one looks helpful too: http://snarfed.org/space/virtual%20host%20redirection Alan K. Holden DetailsDotAt wrote: > With the current install on Ready2Run, everything works fine when > resolving to 'company.com' but with 'www.company.com' it just resovles > a blank white page with no debugging info either. Viewing the source > shows an empty document. > > --~--~---------~--~----~------------~-------~--~----~ Open BlueDragon Public Mailing List http://groups.google.com/group/openbd?hl=en official site @ http://www.openbluedragon.org/ !! save a network - trim replies before posting !! -~----------~----~----~----~------~----~------~--~---
