CalendarXP.net Support

[Vermule]

I need to use the calendar in a secure page. I am not able to do this since the calender is under a non secure protocol.

Has this been ran into before If so, what was the solution

If not, do you have any ideas

[calendarxp]

Well, just make sure you didn't specify "http://" as part of the src attribute of the iframe tag. In other words, always use relative path.

The calendar should work fine no matter you access it via secure or non-secure protocol. e.g. You may navigate our online demo via https.

https://www.calendarxp.net/tt_pop.shtml

[Vermule]

I am still having issues.

The FF error I get is "Permission denied to get property HTMLDocument.getElementById".

The IE error I get is "Access is denied." with the URL of "http://localhost/common/calendar/ipopeng.jsp"

[calendarxp]

What's the code you use for iframe? Do you have an URL for us to test?

BTW, FF will deny access if and only if the iframe is trying to load a document that's not in the same domain as the container page (for security concern). Anyway, we need to see the code in action so as to help you solve the problem.

[Vermule]

Here is the code for the iframe.

[calendarxp]

Well, would you mind sending me the source code of ipopeng.jsp? I also need to see everything under the /common/calendar/ folder (please package them in a zip file).

Also, when you see errors in Firefox, could you please copy me the fully message? And when you click the error link in the javascript console, it should bring you to the line of code where the error was occurred - could you please also tell me which line it is?

Since we can't access it directly, I do need the above info to identify the problem.

Thanks.

[Vermule]

I didn't include my license.js, I didn't think that you would need it.

I included a screen shot of the javascript console for you to see all of the errors.

Thank you again for your help.

[calendarxp]

Thanks for the screen shots.

One quick question - when did those errors show up, before or after you clicking the popup button?

Also, I need you replace the ipopeng.jsp with the original ipopeng.htm and refresh your browser to see if it works.

Finally, I suppose your webpage's url was started with http://localhost/, please let me know if it's not.

[Vermule]

The errors showed up on page load.

I'll try to replace the jsp version with the htm version to see if it still happens.

The webpage's url started https://localhost/, but when I checked the errors in IE it showed the calendar's url as http://localhost/.

[calendarxp]

After you replaced the ipopeng.htm, if the error persists, please add the following javascript to the top of ipopeng.htm:

alert(self.location.href);

After reloading the page you should see a popup with the URL - take a look at the protocol and domain portion and see if they are consistent with the one on your address bar.

[Vermule]

Correct domain, wrong protocol. (See screenshot.)

[calendarxp]

Which web server are you using? We can't seem to be able to reproduce the problem on tomcat 5.0. If you access our website with secure protocol https, e.g. https://www.calendarxp.net, you'll see that all online examples are working well with no errors or exceptions.

After replacing the ipopeng.htm, we got the rest running by re-enabled the gMonths and gWeekDay options in radleft.js and radright.js files. We also added

[calendarxp]

So let's start from scratch - please install the HelloWorld demo from the package in your localhost web server. Then access it through https and see if any error coming up. If no error, then you may proceed to modify it to your favor and test it step by step until you got the error. This way you will know which part of your code is the actual culprit.

[Vermule]

I found out the issue. It was actually an internal security filter that I was not aware of.

Thank you for your help with this issue.