Problem with grid using secured connection (HTTPS)

I need to use the grid in my site, but I also would like to use secure connection (HTTPS).

Unfortunately I noticed some issue that I cannot avoid or solve. While using the grid in secure connection Internet Explorer 6.0 interprets it as a mixed content and there are detected insecure items inside a page.

This caused a standard information in message box about “Secure and insecure items” . I want to avoid this problem without changing a configuration of IE 6.0. There are two reasons of such message: explicit request in HTTP while using HTTPS, and using markups: IFRAME or FRAME without attribute SCR or with empty string value in this attribute (SRC=””). I don’t see such things in grid.js file. I debugged a javascript code of the grid and I noticed that this message is generated just after a function Dispatch call.

I will really appreciate if you will give me some piece of advice, some tips or maybe you already have a solution for this issue.

Thanks for help in advance

The grid does not use absolute URLs and does not use iframes, so it should work on https connection without warnings. Check that the grid stylesheet is also on https url and there are no missing images.

Unfortunately I cannot provide much help with version 1.0. If you are still using it - please consider upgrading to a more recent release. Version 1.0 is no longer maintained or supported.

We tried on the new version and the problem is still occuring:(

- are you using relative URLs for aw.js and aw.css?
- did you copy all content from runtime/styles, not just aw.css?
- when does the warning appear? On load, grid render, later actions?

Could you finally find a solution to this problem? I'm facing exactly the same issue and it is driving me crazy...

In my case the warning is shown using IE 6 when I send an AW.HTTP.Request, any idea?

Jose Luis.

OK, forget about it, there was an iframe without the "src" attribute on the page and thas was causing the warning.

More info here: http://ajaxian.com/archives/ie-frame-bug

Cheers,

Jose Luis.