HTTP PUT for file uploads

[Phillip B Oldham]

Michael wrote:
> On Fri, Aug 01, 2008 at 13:10:46, Phillip B Oldham said...
>
>   
>> Don't want to sound off, but isn't that what FTP was designed for?
>>     
>
> FTP is such an awful protocol to deal with regarding firewalls, I'd much rather
> go the way the original poster is and use HTTP PUT for insecure stuff, and SFTP
> for secure stuff.
>
> But 2GB?  That's huge... a lot for an end-user to just sit and watch without
> clicking reload or something.
>   
Exactly - 2GB is going to be hell to upload. At least with FTP it can 
use multiple ports for data transfer. And with a web interface I'd 
expect users to get annoyed with clicking "back" accidentally or having 
their email-client open a link using the same window. With FTP you can 
"background" the process.

As for firewalls; just use an active connection rather than passive. Job 
done. You'll loose the benefit of the different ports, though.
>   
>> You may have to test this, but I'd assume the maint-stream browsers support 
>> PUT via the XMLHTTPRequest javascript object.
>>     
>
> I was just doing some of this myself yesterday - doesn't seem like there's a
> way to do file uploads with AJAX, but you can easily make a form with a target
> iframe... but this is really offtopic for the nginx list.
>
>   

-- 

*Phillip B Oldham*
The Activity People
phill at theactivitypeople.co.uk <mailto:phill at theactivitypeople.co.uk>

------------------------------------------------------------------------

*Policies*

This e-mail and its attachments are intended for the above named 
recipient(s) only and may be confidential. If they have come to you in 
error, please reply to this e-mail and highlight the error. No action 
should be taken regarding content, nor must you copy or show them to anyone.

This e-mail has been created in the knowledge that Internet e-mail is 
not a 100% secure communications medium, and we have taken steps to 
ensure that this e-mail and attachments are free from any virus. We must 
advise that in keeping with good computing practice the recipient should 
ensure they are completely virus free, and that you understand and 
observe the lack of security when e-mailing us.

------------------------------------------------------------------------
-------------- next part --------------
A non-text attachment was scrubbed...
Name: phill.vcf
Type: text/x-vcard
Size: 261 bytes
Desc: not available
URL: <http://nginx.org/pipermail/nginx/attachments/20080801/111637bb/attachment.vcf>