On Thu, 10 Nov 2005, Mark Adams wrote:
> Simple problem, but might mean a major misconfiguration in Apache.
Which apache would that be? See the next question.
> I have a simple custom error page on my LAN which I have posted here on
> another site for your reference (sans graphic)
> http://adamslan.shyper.com/302.html
Please make clear whether you are reporting misbehaviour on the site
where you are furnishing this thing for alt.html's inspection, or only
on the site which we haven't seen. If it's the latter, then I think
we have insufficient evidence to be able to tell you what's what.
> The problem with this file, and I haven't seen it with any other files, is
> that this thing will display correctly one time after it has been edited or
> Apache has been restarted. Thereafter, it displays only the source code.
Presumably you're not displaying this page for its own sake, but as a
custom error page? So, retrieving it for its own sake might not be a
comparable action to what happens when it's used as a custom error
page. How, exactly, are you using this thing - are you displaying it
*as* a custom 302 error page, or are you configuring the server's
redirection so that it's meant to redirect *to* this page? Or to put
it more simply, "please show us the relevant configuration lines".
Finally, since you haven't named a browser yet, the sceptics amongst
us are going to assume you only checked it in MSIE. How about being a
bit more specific about what you tried, with what, what you expected,
and what in fact you saw?
> I haven't seen anything like this anywhere in Google and I'm not
> seeing anything related to it in any of the logs. The page is just
> about as simple as html gets.
I wouldn't have thought that the details of the HTML are of the
slightest relevance. You yourself already suggested that this was an
Apache configuration problem. Apache isn't normally in the business
of looking inside the static files that you are serving-out: it
decides what to do with them on the basis of its configuration, and,
quite likely on their "filename extension" (if you'll pardon the
expression).
> Can anybody tell me what might be happening?
Anyone got a crystal ball?
good luck
Similar Threads
