httpd-bugs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From bugzi...@apache.org
Subject DO NOT REPLY [Bug 16699] New: - Page cannot be found / Network error when navigating to a page
Date Mon, 03 Feb 2003 12:25:17 GMT
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16699>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=16699

Page cannot be found / Network error when navigating to a page

           Summary: Page cannot be found / Network error when navigating to
                    a page
           Product: Apache httpd-2.0
           Version: 2.0.44
          Platform: PC
               URL: http://www.jiscmail.ac.uk
        OS/Version: Windows NT/2K
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: s.i.warhurst@rl.ac.uk


We have had a problem where a user clicks on a link and they get the following 
errors (2 browsers tested - more prominent on Netscape):

1) On Internet Explorer 5.5 they get a "page cannot be found" page, yet
sometimes if you hit the back button on the browser the page you were trying
to navigate to is actually there in the cache!

2) If they are using Netscape 4.79 they get a "network error" OK dialog box 
come up,
even though the page they were trying to navigate to actually comes up
beneath.

I don't know much about the inner workings of clients/web servers but it's
almost as if the client makes that initial "hello" contact with the web
server, starts retrieving the document (and indeed often gets it) but there
is no "there you are, you've got it now - goodbye" message back from the
server and therefore the client thinks there was an error and throws up page
cannot be found or network error.

The problem seems to happen more when the server is under heavier load but is 
intermittent. It also seems to have only started happening since about Apache 
version 2.035 or 2.036, though that may be coincidental.

In the error logs, there are lots of (>500 a day) lines like this:

"[date/time] [warn] (xxxxxx)The specified network name is no longer 
available.  : winnt_accept: Asynchronous AcceptEx failed."

The server we use is a Pentium 4 2.2Ghz / 1 gig RAM system with a SCSI disk and 
the O/S is Windows 2000 Server SP2. It's connected to a fast network which is 
in turn connected to the net via a >2Gb pipe.

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org


Mime
View raw message