- From: BigBlueHat via GitHub <sysbot+gh@w3.org>
- Date: Thu, 27 Aug 2015 18:10:22 +0000
- To: public-annotation@w3.org
@shepazu sadly "asking the server" involves a separate XMLHttpRequest which may get a completely different response or be prevented altogether (CORS, CSP, etc). The strange fact is that after 20+ years of browser building no one's actually made the originating request data available to code running inside the browser on the results of that request. I find it baffling... There's some likelihood that the new [WHAT WG Fetch API](https://fetch.spec.whatwg.org/) but even that is primarily focused on additional requests--not the original one made by the user. Even within browser extension development it's non-trivial to accomplish, and often relies on watching *every* request that comes through (regardless of it being annotated or not) rather than just asking the current Window/Tab what it's headers were for the current request.... See what I mean? Mind numbing... And, as @azaroth42 just pointed out while I was typing this, you'd have to do an XHR HEAD request for *every* included element in the page that was being annotated. I'd agree that it's unnecessary and inefficient. If a system wants to store it, by all means, but it shouldn't be required. -- GitHub Notif of comment by BigBlueHat See https://github.com/w3c/web-annotation/issues/67#issuecomment-135510094
Received on Thursday, 27 August 2015 18:10:24 UTC