On 1 Dec 2011 at 9:17, Dan Haywood wrote: > Still, if you are hitting issues, then others are bound to.
Hmm - I was in a bit of a hurry and didn't read the info properly. > The main issue (apart from the slightly wacky swing console which appears > because of the simplericity maven plugin that I'm using) is that browsing > to http://localhost:8080/ returns a horrid looking stack trace, whereas if > the user browses to http://localhost:8080/index.html, then (I think) the > experience is quite good. Indeed - the default stack trace looks really bad. Is it a big deal the user "proper" authentication - I'm having issues with being unable to provide custom headers to some of the REST viewers for Firefox (I don't use Chrome). > My thought I had this morning was to write a simple filter that checks the > Accept header, and if it is set to text/html (eg being accessed from a > browser), then do a redirect to index.html. That hopefully will improve > matters. > > Do you agree? Could be, could be... Perhaps turn off authentication completely, for the demo? If possible.
