Updates:
Status: Assigned
Owner: [email protected]
Comment #5 on issue 6003 by [email protected]: FEATURE REQUEST: File upload
by URL
http://code.google.com/p/chromium/issues/detail?id=6003
It seems to me like this feature is misguided. If a website wants to be
able to
accept web content, it could easily ask for a URL and then fetch it itself
(which is
far more efficient than forcing the user's browser to download and then
upload it,
especially when users' upstream bandwidth is often limited and webservers
often have
much better bandwidth anyways.)
Secondly, it seems like it might be frustrating or produce unexpected
results in
certain cases. What if a webserver has htaccess rules set up to
prevent "image
leeching" - e.g. will only serve up the image if the referer matches
something
expected. The user browses to the page with the image, somehow copies the
URL to the
form (drags the image? Copies the URL manually?) and the fetch fails,
because the
referer was incorrect? Or if they're logged in and their session has
expired and they
are requested to log in again (do we upload the login response? that would
be bad. It
also seems scary that you would download something and upload it without any
"preview" to make sure the right thing was being uploaded (the image you
intended,
not some other URL you pasted in or a login form response), and all of that
sort of
breaks the form submission model.
I think this is something that would be much better tackled on the
website's end
(which they can do with existing technologies) than trying to do something
on the
client end. My $0.02
--
You received this message because you are listed in the owner
or CC fields of this issue, or because you starred this issue.
You may adjust your issue notification preferences at:
http://code.google.com/hosting/settings
--~--~---------~--~----~------------~-------~--~----~
Automated mail from issue updates at http://crbug.com/
Subscription options: http://groups.google.com/group/chromium-bugs
-~----------~----~----~----~------~----~------~--~---
