What Do I Do if Protocol Conflicts Arise?
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.
Absolute URLs can be generated for example with a mail page that sends a message to a recipient selected from a list. BSP mail.htm is used for this, and all selected rows are copied to it as parameters. The e-mail address is determined for each selected row, and the mail message is generated using JavaScript.
Note that in the coding, statement window.location = 'mailto:...' is used instead of window.open( 'mailto:...').
SAP recommends that you do not use fully specified URLs, without information about the protocol, host name, domain details and port. Instead, you should always use either absolute or relative URLs, /sap/something/or/another or ../another. The URL is thus collected in the protocol that is currently active and will function correctly both for HTTP and HTTPS.