[twsocket] OnDataAvailable event not firing for UDP client
Hi All, I have a udp client for the TFTP protocol that has worked perfectly since I first wrote it in 1999. Recently we upgraded to Delphi 2010 so I also upgraded to the V7 source code. Unfortunately, things no longer work. I can send the initial request packet to the TFTP server (on the same computer) but after that I do not receive any response packets. I tried my test application written in Delphi 2010 using the DLL compiled with RAD Studio 2007 and the 1999 ICS source and it works just fine. However, the same test application fails to receive any response packets when using the DLL compiled with the V7 source code. Is there something I need to do differently to get the OnDataAvailable event to fire or is there something at a lower level that I can put a break-point in to trace through to the missing packets? Thanks in advance -Mohamed -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] OnDataAvailable event not firing for UDP client
I have a udp client for the TFTP protocol that has worked perfectly since I first wrote it in 1999. Recently we upgraded to Delphi 2010 so I also upgraded to the V7 source code. Unfortunately, things no longer work. Source written 10 years ago will not be aware of Unicode and will assume ANSI strings and pointers. So you must first go through your own source code almost line by line replaced all PChar with PAnsiChar, String with AnsiString, etc, per the various Unicode migration documents. Once you have it working again, can you donate it to the ICS project? We don't currently have a TFTP client (using udp). Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] OnDataAvailable event not firing for UDP client
Hi Angus, I have modified my source code to be Unicode compliant and like I said before, the initial request packet is sent correctly. It's just the response packet that is never detected. Cheers -Mohamed -Original Message- From: twsocket-boun...@elists.org [mailto:twsocket-boun...@elists.org] On Behalf Of Angus Robertson - Magenta Systems Ltd Sent: Wednesday, February 17, 2010 10:23 AM To: twsocket@elists.org Subject: Re: [twsocket] OnDataAvailable event not firing for UDP client I have a udp client for the TFTP protocol that has worked perfectly since I first wrote it in 1999. Recently we upgraded to Delphi 2010 so I also upgraded to the V7 source code. Unfortunately, things no longer work. Source written 10 years ago will not be aware of Unicode and will assume ANSI strings and pointers. So you must first go through your own source code almost line by line replaced all PChar with PAnsiChar, String with AnsiString, etc, per the various Unicode migration documents. Once you have it working again, can you donate it to the ICS project? We don't currently have a TFTP client (using udp). Angus -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
Re: [twsocket] Bug and proposal for fix in TsslHttpCli using proxy
Sorry, sent to early. Here is the rest of the text. I got the version 706 of OverbyteIscHttpProt.pas toady. On line 3638 and 2629 is the source of the problem. When state is httpWaitingProxyConnect and if the answer from proxy contains 200 OK, then the process stops and nothing more happens. My first thougt is to change these lines: ) and not ((StrLIComp(PAnsiChar(FReceiveBuffer), AnsiString('HTTP/1.1 200 OK'), 15) = 0) or (StrLIComp(PAnsiChar(FReceiveBuffer), AnsiString('HTTP/1.0 200 OK'), 15) = 0)) then If the proxy have an errortext to send to the client, I think the proxy sends 200 OK and a document. I think that if we add to these lines that the content-length also have to be 0 all is fixed. Then proxies that answers 200 OK and content-length is 0 (no error) when connection is established will work, and when content-length is more than 0 (proxy send us a description of an error) then we don't continue to send data. Any thoughts on this anyone? Regards Bjørnar Nielsen _ From: Bjørnar Nielsen Sent: 17. februar 2010 21:41 To: ICS support mailing Subject: [twsocket] Bug and proposal for fix in TsslHttpCli using proxy I have found a bug using https through proxy. After connect-command to the the proxy it answers back to the client 200 Connection established. I have come across some proxy-servers that answers 200 OK back to the client. This is a problem for TsslHttpCli. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be
[twsocket] Bug and proposal for fix in TsslHttpCli using proxy
I have found a bug using https through proxy. After connect-command to the the proxy it answers back to the client 200 Connection established. I have come across some proxy-servers that answers 200 OK back to the client. This is a problem for TsslHttpCli. -- To unsubscribe or change your settings for TWSocket mailing list please goto http://lists.elists.org/cgi-bin/mailman/listinfo/twsocket Visit our website at http://www.overbyte.be