Within an SSL connection, the browser displays an error message indicating that the page in question contains both secure and insecure objects, and asks whether the user wants to display the non-secure objects too.
This causes problems when generating URLs in the application, as absolute URLs are generated with the (incorrect) HTTP protocol instead of HTTPS. The usual browser configuration causes the browser to display a warning with an http:// request whenever HTTPS is active.
Answer
Determine the location in the application where absolute URLs are generated. You can find this out using HTTP logging (see Logging in the ICM). Make sure that no more absolute URLs are not generated.