Re: Moving large media files over the internet securily

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

SSL (https) should provide the needed security.

The only problem I can see with large file transfer over the internet
is that one of the connections in the chain b/w server and client might
get closed in the middle of the transfer and thus require resend of the
whole file again.
In order to overcome this you can use (or write your) client that
request ranges of the file and retry the missing range only instead of
the entire file - if the connection was lost, and reassemble the file
parts on the client.

For SSL client you can use HttpWebRequest

HTH

Dekel Israeli

.

Relevant Pages

  • Re: CUPS upgrade from Lenny to Squeeze breaks encryption - HELP
    ... https interface has SSL error ("SSL received a record that exceeded ... attempted on the standard, unencrypted CUPS port. ... from the client. ... which connections on which ports the client is attempting when it ...
    (Debian-User)
  • Re: SFPT With Windows 2000 Server?
    ... doesn't require installing a third party client onto every file transfer ... client workstation. ... > FTPS is FTP with SSL, but I don't think that IIS natively supports it ... >> Would SSL Certificates be a better way to go? ...
    (microsoft.public.inetserver.iis.security)
  • Re: Securing Insecure SMTP
    ... pass the SSL negotiation on the server side. ... I am presented with a client software that attempts to ... accept connections on port 25 instead it uses the SSL smtp port. ...
    (Pen-Test)
  • Java SSL problem
    ... I have a little problem with my SSL file sharing application. ... I've been asked to securised the connections with SSH but I found too ... I use a message server for my application, and a file server per user ... When one client send a file to one server there is no problem. ...
    (comp.lang.java.security)
  • Re: Access 2007->SQL Server2005 "connection was forcibly closed",G
    ... I think it will ameliorate the situation if you clean up the client as ... And to come back to my problem: I think with help of the SQL Server admins ... closed connections - but all of these errors are in the version which used ... Every new client opens again 30 connections if I open 30 tables ...
    (microsoft.public.sqlserver.connect)