On Sep 29, 2011, at 9:27 AM, Phillip Hallam-Baker wrote: > It still needs to at least have an option for specifying the content > type, this could be made optional though.
Why is the content type important for your use cases? It is not inherently linked to the content that you are digesting. There are plenty of types of content that have multiple conflicting MIME types due to history. I foresee that a system that is reading one of these digest: URIs might fail if the content type is not what it expected. --Paul Hoffman _______________________________________________ websec mailing list [email protected] https://www.ietf.org/mailman/listinfo/websec
