Re: URI not accepted

From: JohnTNYC (johntnyc@yahoo.com)
Date: Wed, Aug 25 1999


Message-ID: <004201beeeb5$8a2f4ec0$1300a4d8@nyr.cable.rcn.com>
From: "JohnTNYC" <johntnyc@yahoo.com>
To: "Bless Terje" <link@rito.no>, "'W3C Validator'" <www-validator@w3.org>
Date: Wed, 25 Aug 1999 00:51:47 -0400
Subject: Re: URI not accepted

I rechecked this URI with the validator and it validated fine.  I
checked the response from the IIS server with a "GET /default.asp"
request and it returned:

HTTP/1.1 200 OK
Server: Microsoft-IIS/4.0
Date: Wed, 25 Aug 1999 04:54:35 GMT
Content-Type: text/html
Set-Cookie: ASPSESSIONIDGGGQQGCB=PLJCJOLABFPJOAOHPENHDHBK; path=/
Cache-control: private
... etc

Don't know what the problem may have been before, but the validator does
find the page.  Of course the page does have a bunch of errors, but
that's another story.

John

----- Original Message -----
From: Bless Terje <link@rito.no>
To: 'W3C Validator' <www-validator@w3.org>
Sent: Wednesday, August 18, 1999 12:00 AM
Subject: Re: URI not accepted


> >http://www.hobomedia.com/default.asp
> >
> >It works in all browsers, it seems correct to me, but the
> >validator will not accept it. Is it refusing the .asp, or
> >is it broken?
>
> I assume that by this you mean that the validator spits out "Please
make
> sure you have entered the URI correctly" when you try to validate
(that's
> what I get, anyway). A quick peek at the source indicates that the
validator
> will do that when the server returns a HTTP response that is not 200
("OK"),
> but which isn't 300/301 (redirect) or 401 ("Authentication
required")[0]
> either.
>
> Could someone who is not behind the firewall from hell try telnet to
port 80
> on www.hobomedia.com and check what status code IIS returns for a GET
on
> default.asp? I'm guessing that it's some kind of weird variant "OK"
status
> code (i.e. somewhere in the 20x range) that the validator doesn't
understand
> (it's not really very bright) which makes this a limitation in the
validator
> triggered by "unusual" Microsoft software behaviour.
>
>
> Of course, it could be a lot of other things as well. :-)
>
>
>
> [0] - This, BTW, implies that it doesn't explisitly handle
>       404 "Not found" either and just uses this default
>       catchall for that too!
>