| Home | Software Sales | Crystal KB | Contact Us | 
|
| RDP Support |
|
|||
| RDPWin KB | IRM.Net | RDPWin3 & PCI Compliance | Search | |
Added
8/26/09 TC/SS
Article ID#: KINet0024
Updated: 09/15/09
IRM.Net and Internet Browsers
Return to Index
*** Important Note ****
The login procedure to the IRM.Net owners
pages requires that an authentication cookie be set. If the browser settings
do not allow the authentication cookie to be created, then it is not possible
to login. Browsers configured to block
cookies entirely are not able to login to the IRM.Net owners pages.
IRM.Net and Internet Browsers
IRM.Net does have some limitations when dealing with web browsers. Since there are so many different browsers with so many different capabilities, add-ons, and limitations; IRM.Net is only designed to work with and is tested with the following Internet browsers as of Version 2.092.28: Microsoft's Internet Explorer 7 or 8, Mozilla's Firefox 3.x, Safari 4, and Chrome 2 or 3.
Safari
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:
- Configure the browser to 'Always' accept cookies.
- Set up the IRM.net server as a subdomain of the marketing site (for example: www.resortdata.com and irm.resortdata.com)
- Provide access to IRM.Net owners via a hyperlink rather than inside an iframe
| Support Home | RDPWin3 & PCI Compliance | Enhancement Requests | Open A Web Support Ticket |
|---|---|---|---|
| Training | 3rd Party Interfaces | RDP Sales Website | Contact Us |
 |