My application's base page does checking against the user agent string to
redirect unsupported browsers to a "support" page.  The problem we're seeing
is that WicketTester is using a hardcoded user agent from a crazy-old
version of firefox.

Is there any recommended way to specify the user-agent used by WicketTester,
or is this a known limitation?  From what I can tell, there doesn't seem to
be a way to get at the actual header data to make the change.

Reply via email to