I did the mistake of creating my entire web application and not testing it on IE along the way. I only tested it on Firefox and Safari. The web app runs fine on both Safari and Firefox but it gives a Permission Denied error on IE.

I am using Google AuthSub authentication and so for authenticating using Google Account, it first redirects to allow the app access to Google Account. After authentication, IE changes 'http' to 'https'. This does not happen with either Firefox or Safari. They remain with the 'http' protocol.

IE then gives a Permission Denied error. Is the JavaScript conflicting with 'https' in any way?

The app is here ->

and the error-causing page is -> .php

I did the mistake of creating my entire web application and not testing it on IE along the way. I only tested it on Firefox and Safari. The web app runs fine on both Safari and Firefox but it gives a Permission Denied error on IE.

I am using Google AuthSub authentication and so for authenticating using Google Account, it first redirects to allow the app access to Google Account. After authentication, IE changes 'http' to 'https'. This does not happen with either Firefox or Safari. They remain with the 'http' protocol.

IE then gives a Permission Denied error. Is the JavaScript conflicting with 'https' in any way?

The app is here -> http://ankitahuja./apps/proxycal

and the error-causing page is -> http://ankitahuja./apps/proxycal/proxycal.php

• javascript
• internet-explorer
• https

Share Improve this question Follow asked Mar 7, 2009 at 5:50 ankitankit 1,33333 gold badges1313 silver badges1212 bronze badges

Add a ment  | 

3 Answers 3

Sorted by: Reset to default 1

When I open up the proxycal.php page in both IE and FF, an error is raised on this line in the Javascript (in function _run):

calendarService = new google.gdata.calendar.CalendarService('proxycal');

Here, calendar is not a member of google.gdata.

I suggest you debug through the call stack to find out what is not being initialized.

I've run into that error before in IE. Most often, it was because I was fetching data from another domain using XmlHttpRequest. Check the "allow data from other domains" setting in IE's Internet Options, make sure it's allowed and then see if you get the same error.

In IE you can use XDomainRequest, but not for https from http, which is blocked and This is an expected by-design behavior (though not expected in FF/Chrome)