www-apache-bugdb mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tim Cares" <tca...@websidestory.com>
Subject RE: general/6991: ErrorDocument directive must include full, not relative path
Date Tue, 19 Dec 2000 17:50:01 GMT
The following reply was made to PR general/6991; it has been noted by GNATS.

From: "Tim Cares" <tcares@websidestory.com>
To: <slive@apache.org>, <apache-bugdb@apache.org>
Cc: <apbugs@apache.org>
Subject: RE: general/6991: ErrorDocument directive must include full, not relative path
Date: Tue, 19 Dec 2000 09:48:10 -0800

 It appears as though it only happens on IE 5.X and up...I tested on 6
 separate client machines and this behavior was duplicated on all of them.
 Netscape browsers and older IE browsers did not display this problem.
 
 -----Original Message-----
 From: slive@apache.org [mailto:slive@apache.org]
 Sent: Monday, December 18, 2000 10:39 PM
 To: apache-bugdb@apache.org; slive@apache.org; tcares@websidestory.com
 Subject: Re: general/6991: ErrorDocument directive must include full,
 not relative path
 
 
 [In order for any reply to be added to the PR database, you need]
 [to include <apbugs@Apache.Org> in the Cc line and make sure the]
 [subject line starts with the report component and number, with ]
 [or without any 'Re:' prefixes (such as "general/1098:" or      ]
 ["Re: general/1098:").  If the subject doesn't match this       ]
 [pattern, your message will be misfiled and ignored.  The       ]
 ["apbugs" address is not added to the Cc line of messages from  ]
 [the database automatically because of the potential for mail   ]
 [loops.  If you do not include this Cc, your reply may be ig-   ]
 [nored unless you are responding to an explicit request from a  ]
 [developer.  Reply only with text; DO NOT SEND ATTACHMENTS!     ]
 
 
 Synopsis: ErrorDocument directive must include full, not relative path
 
 State-Changed-From-To: open-feedback
 State-Changed-By: slive
 State-Changed-When: Mon Dec 18 22:38:31 PST 2000
 State-Changed-Why:
 
 I strongly suspect that this is a client issue, and
 not a server issue.  Can you recreate this behaviour
 with different clients, or by using "telnet" to
 request the pages from the server?  Apache has
 no concept of whether or not a request is the "first"
 one, so it cannot have different behaviour of
 first and later requests.
 
 
 

Mime
View raw message