next »

[bwells]

I have a web page with two calendars. One calendar is full of information, the other is empty. If a person clicks on the button to see the calendar that is full, sometimes they will get "The page cannot be displayed" error message instead of the calendar. I get this error often from my XP machine, but not from my windows 2000 machine (so far). And on my XP machine, if I refresh the page a few times, I will eventually get the calendar to show. On the other hand, the calendar that has no content comes up fine all the time.

And if I type in directly the URL for the cgi script, both calendars come up fine. The problem only shows up if I go to the calnedar using the button.

The url for the page I am having problems with is:
http://www.leapinlizards.biz/classes.htm

The button for the Brunswick is full of dates and the button for Portland calendar is empty.

It is as if when the Brunswick button is pressed, the server times out waiting for the CGI script to run. But the time it takes for the error page to show is only a couple of seconds.

What causes "The Page Cannot Be Displayed" error to be returned?  Why would this happen only some time and only from certain clients?

I would appreciate any help anyone can offer. This would be easier to fix if it always failed, but it seems to be tied to something I dont have much control over.  I would like to understand what is wrong before I contact the web hosting technical support.  Is there anything about running a cgi from a button press which would cause this kind of behavior?

thanks
Bryan

[DanO]

** It is as if when the Brunswick button is pressed, the server times out waiting for the CGI script to run. **

Are there any error messages in the server's error log at those times?

** The problem only shows up if I go to the calnedar using the button. **

I don't see how that would make a difference. Did you check the URL in your browser's location field to make sure it's correct?

Dan O.

------------------

[bwells]

I have not checked the server log yet.  

One thing I tried which seemed to change the way things worked today was to make the button link to the fully qualified URL like http://www.leapinlizards.biz/calendar/calendar.cgi  instead of calendar/calendar.cgi.  I had it as a relative path before, but when I changed it to a fully qualified path, the server seems to wait longer for the page to load and now it seems to be working correctly.  I know that by using the relative path vs the http:// path, it changes the way the server loads the page and perhaps this explains what I saw?

------------------

[DanO]

** I know that by using the relative path vs the http:// path, it changes the way the server loads the page **

It shouldn't as it is the browser which calls the server and a browser would have to provide a fully qualified URI to the server or it wouldn't be able to load the page at all.

Dan O,

------------------