- From: <bugzilla@jessica.w3.org>
- Date: Tue, 03 Dec 2013 16:15:14 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=23946
Arun <arun@mozilla.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |WONTFIX
--- Comment #7 from Arun <arun@mozilla.com> ---
In general, with blob: URLs there has been a trade-off between including the
entirety of the range of HTTP behavior (by including more request-response
options, for example) and keeping a limited protocol with tangible use cases in
mind.
The argument for having a versatile protocol (e.g. adding all of HTTP's
headers, or even including stuff from HTTP URLs, like query) really hinges on
future uses, which haven't emerged yet. Additionally, it comes with the risk
of introducing security implications that HTTP has resolved over much use.
On balance, I prefer use-case driven bugs as a pragmatic and safe approach to
expanding the blob: protocol. We're free to introduce changes over time. I'm
marking this closed. Please re-open or file a different bug when the need
arises.
--
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 3 December 2013 16:15:21 UTC