Support crossdomain.xml and other root resources

[GoogleCodeExporter]

Flash/Flex look for a file "/crossdomain.xml" to determine whether to 
permit a flash app to communicate across domains.  If the web app being 
tested has a context other than "/" (in particular, if it must have a 
context other than "/"), then it can not serve files from the root, which 
makes it difficult to test Flash applications that require cross domain 
communication.

Add some kind of support for serving files from the root context.

Original issue reported on code.google.com by James.Sy...@gmail.com on 1 Jun 2009 at 3:05

[GoogleCodeExporter]

Original comment by tonylovejava on 30 Jun 2011 at 1:33

• Added labels: feature

[GoogleCodeExporter]

This could have been fixed by the user by employing the eventual solution to 
issue#9 (and currently also by a suggestion in issue#85). Those issues suggest 
that one should be able to tailor the Jetty server that is started by being 
able to specify a jetty.xml to run (or, in my suggestion, to be able to "add 
in" such extra jetty.xml's).

You would then "force" in a '/' context using the jetty config (you can do 
everything with this config language - it is actually just a "java in xml" 
translation tool).

Original comment by en...@stolsvik.com on 29 Jul 2011 at 7:05

[GoogleCodeExporter]

i looking for this answer too, can anyone can place a example extra jetty.xml 
file? thanks

Original comment by sendre...@gmail.com on 6 Feb 2015 at 1:03

[GoogleCodeExporter]

is there any example jetty.xml for support crossdomain.xml? i am a newer, right 
now i not use jetty.xml just set my webapp's context path to "/" and place the 
crossdomain.xml to src/main/webapp folder. it can be work, but i think it will 
be a better way. any one can help me? thanks

Original comment by sendre...@gmail.com on 6 Feb 2015 at 1:29