On Sat, 3 Nov 2007, Adam Barth wrote:
One scenario where something like this would be useful is for a site
like eBay that serves iframes and img tags pointing to third-party
content after reviewing that content for malware, scams, and adult
content. Without this mechanism, the content
On 11/5/07, Ian Hickson [EMAIL PROTECTED] wrote:
Philip brought up a good point on IRC which is that hashing the entity
doesn't protect against changes to the headers (and hashing the headers
isn't workable since they change).
I'm not sure it's worth it.
Those are good use cases, though.
On Mon, 5 Nov 2007, Jon Barnett wrote:
On 11/5/07, Ian Hickson [EMAIL PROTECTED] wrote:
Philip brought up a good point on IRC which is that hashing the entity
doesn't protect against changes to the headers (and hashing the headers
isn't workable since they change).
If it were to be
On Wed, 25 Jan 2006, Mike Hoye wrote:
Hi, all. I hope this hasn't been proposed before, but if it is my
googlage is failing me. My proposal is for the addition of a validate
attribute to the the a element that would let the client verify the
content of a link as it comes in, and either
On Nov 3, 2007 2:31 AM, Ian Hickson [EMAIL PROTECTED] wrote:
On Wed, 25 Jan 2006, Mike Hoye wrote:
The validate attribute would describe an algorithm to employ and a
result to compare it to; for example, somebody downloading the en-US
version of FF 1.5 from the Mozilla.com homepage could
On Thu, Jan 26, 2006 at 06:15:06AM +0600, Alexey Feldgendler wrote:
On Thu, 26 Jan 2006 03:14:07 +0600, Mike Hoye [EMAIL PROTECTED]
wrote:
The validate attribute would describe an algorithm to employ and a result
to compare it to; for example, somebody downloading the en-US version
of FF
On Thu, 26 Jan 2006 03:14:07 +0600, Mike Hoye [EMAIL PROTECTED]
wrote:
The validate attribute would describe an algorithm to employ and a result
to compare it to; for example, somebody downloading the en-US version
of FF 1.5 from the Mozilla.com homepage could click on a link like
[a
