Regarding the blank.html file

Poster: grenner
Dated: Friday October 29 2004 - 13:43:15 BST

Hi, we are having difficulty with the menu on an SSL server. I read about the blank.html file and was wondering where we need to put the file in order to make the menus work properly. It looks like we are supposed to have the blank.html file at the root level of the site but we want to put all of our scripts in a sub-folder. Is it as simple as changing the mmenudom.js file to reflect the appropriate path for the blank.html file? Can we change the string " src=/blank.html" to " src =/nbp/scripts/blank.html"? Does that break the code if we do this?

We are also trying to get an understanding of why this secure/unsecure message is generated in the first place. We think that the server is looking for blank.html, not finding it, then it tries to throw a 404 error. Our question is what is actually generating the secure/non-secure message? Is it the 404 page? We are wondering if we need to adjust our server configuration.

Also our system architect was wondering what the blank.html file is for? Is it something we absolutely need to get the menus to work in an SSL environment or can we just delete references to it from the code altogether. What is it's purpose?

Unfortunately our menus are being used on an intranet environment so you wouldn't be able to view them. However, we have purchased a license.

Thanks in advance,

Sincerely,
Gavin Andrew Renner

Re: Regarding the blank.html file

Poster: kevin3442
Dated: Monday November 1 2004 - 21:55:46 GMT

Hi Gavin,

That's correct. Place the blank.html file that came with the download in the site's root.


I suppose you could do that, but there really shouldn't be a need. If your goal is to keep all of your scripts in a /scripts folder then this shouldn't be a concern, since blank.html isn't a script; it's just a blank html file. I don't think editing the .js file as you've suggested will "break" anything, but it does do two things that you might not like: (1) editing the source code nullifies the support agreement, and (2) if you edit mmenudom.js then you will have to apply the same edit every time you get a source code update and upload it to your site. To me, that'd be an administrative pain, not worth the time. Plus, suppose you forget to apply the edit one time; next thing you know you're back to having problems with SSL.


The menu code creates a hidden iframe under some circumstance to make sure that your menus display correctly (e.g., so that they don't open behind a radio button). In IE, an iframe without its src attribute set defaults to the IE about page, which (ask MS why) loads as an insecure page in https://. The workaround suggested by MS is to src a dummy page into the iframe (hence, blank.html). YOu can read more about it in this Microsoft article.


See above. Again... editing menu source code nullifies the support agreement. Also, I would think it a bad idea to delete source code.

Hope that helps,

Kevin