W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2010

[Bug 7918] prefetching: allow site to deny

From: <bugzilla@jessica.w3.org>
Date: Wed, 12 May 2010 16:19:07 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1OCEeJ-0005Md-9U@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=7918





--- Comment #12 from Nick Levinson <Nick_Levinson@yahoo.com>  2010-05-12 16:19:06 ---
I support reopening. Thanks.

Universalizing from X-Moz might be good.

One concern, but maybe I misunderstand something: If X-Moz results in the TCP
connection being closed and Google says to send a 404 error for X-Moz, does
that interfere with fetching when the time comes for a timely fetch of the same
file that denied prefetch? And does sending a 404 error interfere with viewing
the current page? I'm unclear why a 404 error is supposed to be helpful to the
visitor for a prefetch denial if fetching will proceed. Prefetch denial could
be stated in a status bar, if that's helpful and wouldn't interfere with
current-page viewing or timely fetching.

I'm happy with any solution that works. If there's a better way than a use.txt
file, great.

Thank you.

-- 
Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
Received on Wednesday, 12 May 2010 16:19:08 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 12 May 2010 16:19:09 GMT