I just noticed one more thing. This only seems to happen in IE. Mozilla (well, FireFox at least) seems to work fine.

Thomas Lockney wrote:

I'm encountering a strange problem that we didn't see until we began running our site behind an IIS server with SSL enabled. The way our application is set up we have certain items in the menu which need to display in a new window (e.g., help). To accomplish this task, we've been using the location attribute in the menu-config.xml file and passing in 'javascript:openNewWindow();' as the value with openNewWindow() being a javascript function which is defined in a global js file accessible to all pages.

When running directly from the application server or even proxied through IIS, this all works fine. However, when we add SSL into the mix, the browser seems to be attempting to access 'https://theserver/contextName/javascript:openNewWindow();', which clearly doesn't work. Has anyone seen this sort of behaviour or does anyone have any ideas on a possible solution?

Thanks,
Thomas Lockney




------------------------------------------------------- SF.Net is sponsored by: Speed Start Your Linux Apps Now. Build and deploy apps & Web services for Linux with a free DVD software kit from IBM. Click Now! http://ads.osdn.com/?ad_id=1356&alloc_id=3438&op=click _______________________________________________ struts-menu-user mailing list [EMAIL PROTECTED] https://lists.sf.net/lists/listinfo/struts-menu-user

Reply via email to