On Thu, 4 Nov 2004 16:36:04 -0500, Joe Gregorio <[EMAIL PROTECTED]> wrote:
The only solution that I can see right now that avoids all of these problems is that the ERROR method be used and that it only be used on the URI of the feed itself.
I've thought this is the best solution all along, so I'm needless to say; +1 on this. It would be nice to be able to ERR a different URI, though, since not all feeds are served by something that can do anything with an incoming ERR request but still would want to (e.g. static files).
The general and recommended practice should be to ERR the erronous resource, but another mechanism should be available, imho. What we can do to restrict the usage on the ErrorURI is to say that it MUST be in the same domain as the erronous resource. If the domain in the URI of the 'X-Error-URI' header is different from the domain in the URI of the resource, the client MUST NOT do an ERR request to the URI.
If we do this then I think it should be written as an I-D outside of this WG.
I think so as well.
-- Asbj�rn Ulsberg -=|=- [EMAIL PROTECTED] �He's a loathsome offensive brute, yet I can't look away�
