[Bug 25914] No definition of parsing blob's scheme data

https://www.w3.org/Bugs/Public/show_bug.cgi?id=25914

--- Comment #12 from Glenn Maynard <glenn@zewt.org> ---
Oh, forgot about the nested-URL aspect of blob URLs now.  The scheme data (if I
read correctly) of "blob:http://foo.com/1111-2222?data" is
"http://foo.com/1111-2222".  Should the scheme data just be recursively parsed
as a URL, so it can retrieve the origin of any nested scheme?

Speaking of which, the "blob:origin/UUID" encoding assumes that "origin/path"
makes sense for every possible scheme that can be an origin for blob URLs.  Is
that safe?  I can't think of any where it won't, but if a URL doesn't have a
"host/path" formatting at all it could be weird.  (data: is a URL format that
doesn't, but I haven't been following the origin-of-data: discussion to know if
that matters.)

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Thursday, 5 June 2014 13:46:57 UTC