IRM.Net and Internet Browsers
Return to Index

By default, Safari is configured to accept cookies 'Only from sites you navigate to' (which does not include an iframe of a different domain than the parent).  So, when IRM.Net is in an iframe and the domain of the IRM.Net is different than that of the parent page (for example www.resortdata.com and irm.rdp.com) and Safari is configured in this way, the authentication cookie cannot be created and it is not possible to login to the IRM.Net owners page.  

To workaround this issue several options are available:

1. Configure the browser to 'Always' accept cookies.
2. Set up the IRM.net server as a subdomain of the marketing site (for example: www.resortdata.com and irm.resortdata.com)
3. Provide access to IRM.Net owners via a hyperlink rather than inside an iframe.

Update 12/12/12: RDP no longer recommends placing the IRM.Net in an iframe. The reason for not using an iframe is that the browser SSL lock icon will not display when IRM.Net is in an iframe (unless the marketing website also has an SSL). This has the potential for lost bookings because guests cannot see that your site is secure. Also, with the iframe, it very difficult to avoid the double scroll bars, which can be confusing and hard to maneuver. 

Instead, a custom theme should be used to style the IRM.Net to complement or mirror the marketing website. Use the customizable Bannerheader.htm and Bannerfooter.htm files to add images and link back to the marketing site, or use the same links as the marketing site's banner and/or footer. Code the marketing site link to the IRM.Net to open in new tab or just navigate through to it. For details on creating a custom theme, see IRM.Net Custom Themes.