- From: Gerald Oskoboiny <gerald@w3.org>
- Date: Thu, 2 Nov 2000 13:48:06 -0500
- To: W3C Validator <www-validator@w3.org>
On Thu, Nov 02, 2000 at 08:47:04AM -0500, Hugo Haas wrote: > On Thu, Nov 02, 2000, Terje Bless wrote: > > >Yes, if a document is in a private space and it has a bunch of links in > > >the same area, the link checker will report those links as 401's. This is > > >because the link checker to check technical reports which are public. > > > > But don't you proxy the auth request for the original document to the > > browser? Why not cache that and attempt to use it for the relative links > > within the same realm? The only time this would create a problem is with a > > public document that links to private documents. > > That's an excellent point: 401's should be reported only if the realm is > different from the one for the document checked. One problem with this though is that there may be some 401s that are a result of the draft being (temporarily) in member space, and others that are actually links to other member-internal resources that need to be reported. How about an option that says "ignore 401s for resources that have the same URI prefix as that being checked" or something? -- Gerald Oskoboiny <gerald@w3.org> +1 613 261 6630 System Administrator http://www.w3.org/People/Gerald/ World Wide Web Consortium (W3C) http://www.w3.org/
Received on Thursday, 2 November 2000 13:48:07 UTC