Re: [twsocket] TSslWSocketClient Download

2011-10-21 Thread daniel legrand
Hi, Thanks for the response. First question, Do we have any ftps server demo project? Second question, Is it possible to change FTP port to for example 51200? Any demos for SSLFTPServer? I have done some FTP client stuff before but never done anything with the ftp server or sslftp server.

Re: [twsocket] HttpServer and Server-push?

2011-10-21 Thread Angus Robertson - Magenta Systems Ltd
I presume there is another way to get to the posted data apart from the method demonstrated in the webserver demo? I have updated the web server demo with a new page delayed.html which is sent after a 10 second delay using a timer, as I previously explained you need to use. This is actually

Re: [twsocket] Suggestion for DocumentToContentType

2011-10-21 Thread Angus Robertson - Magenta Systems Ltd
I also find myself with the need to edit the DocumentToContentType function, each time I update my local copy of ICS. SVN has been updated with a new OverbyteIcsHttpSrv: Oct 21, 2011 V7.41 Angus added OnHttpMimeContentType to allow custom ContentTypes to be supported for unusual file

[twsocket] Purposal to remove the none finished .NET code from a cross platform ICS (IPv6 branch)

2011-10-21 Thread Arno Garrels
Hi, With upcomming cross platform support new IFDEFs are required. The V7 DotNet port Francois committed a few years ago has never been finished and in the meanwhile a lot of development took place with zero care about .NET compatibility. As a result current .NET state is in a very bad state

Re: [twsocket] Suggestion for DocumentToContentType

2011-10-21 Thread RTT
On 21-10-2011 19:18, Angus Robertson - Magenta Systems Ltd wrote: Oct 21, 2011 V7.41 Angus added OnHttpMimeContentType to allow custom ContentTypes to be supported for unusual file extensions. Seems to be working, but why the heck you call the internal DocumentToContentType, even if it is

Re: [twsocket] Suggestion for DocumentToContentType

2011-10-21 Thread Lars Gehre
Oct 21, 2011 V7.41 Angus added OnHttpMimeContentType to allow custom ContentTypes to be supported for unusual file extensions. Very nice. Is there a reason you placed the calls in this sequences? I think procedure THttpConnection.SendDocument[..] begin ErrorSend := FALSE;

[twsocket] THTTPCli fail to resolve URLs that start with //

2011-10-21 Thread RTT
According to the rfc1808.txt, an URL can start with // The ParseURL function will fail in such cases. Also, during a relocation, the THTTPCli fail to parse a location field with such URLs. Here is an example, that result in a relocation with these characteristics