Re: Gives 404 Error on Page that exists
On Tue, 21 Jun 2005, Harrie wrote:
[color=blue][color=green]
> > So what do *you* expect an error page to look like?[/color]
>
> I don't have an answer to that, but I didn't expect to see a page with
> "content" ("non error" content that is).[/color]
OK, this seems to have been a mutual misunderstandin g. I hadn't
tested the actual site, so I was following up on the basis of what I
was reading in the posting.
[color=blue]
> That's why I was expecting anything else than an actual page which
> looks normal.[/color]
OK, I thought you were expecting the browser to react in some special
way.
Normally, it just "renders the content body", whatever that may
contain. What it contains is determined by the server configuration.
It may be conventional to refer to the error code and reason text and
so on - but that's not an absolute requirement. You'll find plenty of
servers which respond to any 404 condition with an advertisement for
their sponsors, for example...
There *should* be some indication, somewhere, that the transaction did
not end with 200 OK, but in practice that tends to be a bit
inconspicuous. However, if you're scripting a web retrieval (for
example, wget) then the software will take more care over this
distinction!
[color=blue][color=green]
> > [..] (unless you're BillG, of course - then the rule would be[/color][/color]
to toss away[color=blue][color=green]
> > the informative detail, and invent some misleading explanation of his
> > own...).[/color]
>
> Are you really, Really, REALLY sure? ;)[/color]
"Try again later" ?
On Tue, 21 Jun 2005, Harrie wrote:
[color=blue][color=green]
> > So what do *you* expect an error page to look like?[/color]
>
> I don't have an answer to that, but I didn't expect to see a page with
> "content" ("non error" content that is).[/color]
OK, this seems to have been a mutual misunderstandin g. I hadn't
tested the actual site, so I was following up on the basis of what I
was reading in the posting.
[color=blue]
> That's why I was expecting anything else than an actual page which
> looks normal.[/color]
OK, I thought you were expecting the browser to react in some special
way.
Normally, it just "renders the content body", whatever that may
contain. What it contains is determined by the server configuration.
It may be conventional to refer to the error code and reason text and
so on - but that's not an absolute requirement. You'll find plenty of
servers which respond to any 404 condition with an advertisement for
their sponsors, for example...
There *should* be some indication, somewhere, that the transaction did
not end with 200 OK, but in practice that tends to be a bit
inconspicuous. However, if you're scripting a web retrieval (for
example, wget) then the software will take more care over this
distinction!
[color=blue][color=green]
> > [..] (unless you're BillG, of course - then the rule would be[/color][/color]
to toss away[color=blue][color=green]
> > the informative detail, and invent some misleading explanation of his
> > own...).[/color]
>
> Are you really, Really, REALLY sure? ;)[/color]
"Try again later" ?
Comment