Bug Fix: Delphi 7 indy 9.0 IndyFTP ReadTimeout is not work (idFTP.pas)

delphi

    Sponsored Links

    Next

  • 1. Boundary property unknown
    Hi, I want to read the boundary property of a messagepart like this: idMessage.messageparts[index].boundary. Although I found many samples with this code, and it's also in the helpfile, the property boundary is unknown. (Latest Indy snapshot and Delphi 2007). What am I doing wrong? Thanks. Uli
  • 2. HTML Attachments in POP3 (Indy 10)
    I'm using this code to save the body of the email and the attachments. If the attachment is a HTML document, the code will save it as the email body (in the "body text" part of the code). I compiled the same code in Indy 9, and the HTML attachment was saved as an attachment (in the "general attachment" part of code). How should I handle html attachments in indy 10? Can somebody send me a sample code please? I have latest Indy 9 and Indy 10 installed. TIA, -ioan FilePrefix := MakeUniqueCorrelation(AppPath); for i := 0 to AMsg.MessageParts.Count - 1 do begin if (AMsg.MessageParts.Items[i] is TIdAttachment) then begin //general attachment TIdAttachment(AMsg.MessageParts.Items[i]). SaveToFile(TIdAttachment(AppPath + 'inbox' + PathDelim + AMsg.MessageParts.Items[i]).Filename); end else begin //body text if AMsg.MessageParts.Items[i] is TIdText then begin TIdText(AMsg.MessageParts.Items[i]).Body. SaveToFile(AppPath + 'inbox' + PathDelim + FilePrefix + '.bdy'); end end; end;
  • 3. Post long text data to an ASP page
    Hi, I'm trying to post long text data to an ASP page using the Indy IdHTTP component. Using the following code I'm able to post data, but its length seems to be limited... TMemoryStream *aStream = new TMemoryStream(); TStringStream *Params = new TStringStream(""); IdHTTP1->Request->ContentType = "application/x-www-form-urlencoded"; Params->WriteString(URLEncode("destinatario="+IdMessage1->Recipients- >EMailAddresses)); Params->WriteString(URLEncode("&mittente="+IdMessage1->From- >Address)); Params->WriteString(URLEncode("&oggetto="+IdMessage1->Subject)); Params->WriteString(URLEncode("&messaggio="+IdMessage1->Body->Text)); try { IdHTTP1->Post(ServerCSNews+"invia_es.asp",Params,aStream); aStream->WriteBuffer("\0", 1); risp=PChar(aStream->Memory); } __finally { delete aStream; delete Params; } Have you got any idea to post without length limit? Thank you very much in advance
  • 4. Indy Examples sending messages between server and client
    Are there any Indy examples using simple messages between a a server pc and many client pcs. The server will be using an Indy tcp server component and the clients will use either a tcp server or a non server component. These components will either send simple text or record structures. Initially I can focus on simple text. The server needs to be able to send a message to the client at any time. The message will just be a flag that will signal the client that a message needs to be picked up from the server. Once this signal has been received, the client will send a request to the server for any waiting messages. This makes me think that the client PC needs to have an Indy server component or perhaps a client component with a timer to look for the flag that there is a message. If there are any examples that make use of Indy in this type of process I would certainly appreciate a link or any insight as to the best approach to take in this endeavor.

Bug Fix: Delphi 7 indy 9.0 IndyFTP ReadTimeout is not work (idFTP.pas)

Postby fluber » Mon, 12 Nov 2007 17:28:51 GMT

Dear All:

   When use idftp to get a file from ftp server and the wireless ap is
shutdown,  the idftp seems to in the endless loop.
and do detect this case, not raise a timeout exception.
   I already set the ReadTimeout property of IdFTP Component, but
seems not work. I decide to trace the source code
and I found the procedure TIdFTP.InternalGet has a bug in the
following code section.

        with TIdSimpleServer(FDataChannel) do begin
          TIdSimpleServer(FDataChannel).ReadTimeout :=
self.ReadTimeout;   / / I add this line
          InitDataChannel;
          BoundIP := (Self.IOHandler as
TIdIOHandlerSocket).Binding.IP;
          BeginListen;
          SendPort(Binding);
          if AResume then begin
            Self.SendCmd('REST ' + IntToStr(ADest.Position), [350]);
{Do not translate}
          end;
          Self.SendCmd(ACommand, [125, 150, 154]); //APR: Ericsson
Switch FTP
          Listen;
          ReadStream(ADest, -1, True); // make this proceduer logic
error
        end;

In this secion create a TIdSimpleServer object but not initialize the
ReadTimeout property, so that make ReadStream logic error.
ReadStream will call ReadBuffer and will call ReadFromStack.



function TIdTCPConnection.ReadFromStack(const
ARaiseExceptionIfDisconnected: Boolean = True;
 ATimeout: Integer = IdTimeoutDefault; const ARaiseExceptionOnTimeout:
Boolean = True): Integer;
// Reads any data in tcp/ip buffer and puts it into Indy buffer
// This must be the ONLY raw read from Winsock routine
// This must be the ONLY call to RECV - all data goes thru this method
var
  i: Integer;
  LByteCount: Integer;
begin
  if ATimeout = IdTimeoutDefault then begin
    if ReadTimeOut = 0 then begin
      ATimeout := IdTimeoutInfinite;
    end else begin
      ATimeout := FReadTimeout;  // if donot add the
"TIdSimpleServer(FDataChannel).ReadTimeout := self.ReadTimeout;  "
this value will be zero
    end;
  end;


B.R.

Fluber Wang


Bug Fix: Delphi 7 indy 9.0 IndyFTP ReadTimeout is not work (idFTP.pas)

Postby fluber » Mon, 12 Nov 2007 17:30:28 GMT

Dear All:

   When use idftp to get a file from ftp server and the wireless ap is
shutdown,  the idftp seems to in the endless loop.
and do detect this case, not raise a timeout exception.
   I already set the ReadTimeout property of IdFTP Component, but
seems not work. I decide to trace the source code
and I found the procedure TIdFTP.InternalGet has a bug in the
following code section.

        with TIdSimpleServer(FDataChannel) do begin
          TIdSimpleServer(FDataChannel).ReadTimeout :=
self.ReadTimeout;   / / I add this line
          InitDataChannel;
          BoundIP := (Self.IOHandler as
TIdIOHandlerSocket).Binding.IP;
          BeginListen;
          SendPort(Binding);
          if AResume then begin
            Self.SendCmd('REST ' + IntToStr(ADest.Position), [350]);
{Do not translate}
          end;
          Self.SendCmd(ACommand, [125, 150, 154]); //APR: Ericsson
Switch FTP
          Listen;
          ReadStream(ADest, -1, True); // make this proceduer logic
error
        end;

In this secion create a TIdSimpleServer object but not initialize the
ReadTimeout property, so that make ReadStream logic error.
ReadStream will call ReadBuffer and will call ReadFromStack.



function TIdTCPConnection.ReadFromStack(const
ARaiseExceptionIfDisconnected: Boolean = True;
 ATimeout: Integer = IdTimeoutDefault; const ARaiseExceptionOnTimeout:
Boolean = True): Integer;
// Reads any data in tcp/ip buffer and puts it into Indy buffer
// This must be the ONLY raw read from Winsock routine
// This must be the ONLY call to RECV - all data goes thru this method
var
  i: Integer;
  LByteCount: Integer;
begin
  if ATimeout = IdTimeoutDefault then begin
    if ReadTimeOut = 0 then begin
      ATimeout := IdTimeoutInfinite;
    end else begin
      ATimeout := FReadTimeout;  // if donot add the
"TIdSimpleServer(FDataChannel).ReadTimeout := self.ReadTimeout;  "
this value will be zero
    end;
  end;


B.R.

Fluber Wang


Similar Threads:

1.Fixed bugs IdCookies.pas, IdCookieManager.pas

Hello Indy users and Indy experts.

I use Indy 9.0.14 (D5)
After torture tests, i've noticed some bugs for cookies management :
- subdomains are not supported :a cookie available for mydomain is
considered as not valid (isvalidcookie) for subdomain.mydomain
- domains and paths not correctly managed by TidCookieManager : when a
cookie is added to the cookies collection, it's added to a cookiesbyDomain
section which is a TStringList for a particular domain. Inside this section,
only the name is considered and not the path.
- The generateCookie list method doesn't support cookies for same domain but
different paths (like prior bug)
- The Cookie collection is not or can't be correctly freed : The
cleanUpCookieList method only drops expired cookies on the fly and when the
component is destroyed. Even in this case, only cookies objects are freed
but not Tstring items

All have been reported in bbg section for indy team, and this news group,
but because Indy team was to busy, i had to fix theses bugs by myself...
As chad suggested, i post this message :
1/ for indy experts to check this with me and eventually integrate the fixed
units
2/ for other users that have theses problems too and want a quick solution.



FLX.


2.[Q] Converting Delphi 6 Indy 8.xx to Delphi 2006 Indy 10.xx

G'Day,

I have a whole heap of old Delphi 6 code that is based on Indy 8.xx
that I need to convert to Delphi 2006 Indy 10.xx. Naturally the
architecture has changed between 8.xx and 10.xx. Is there a conversion
guide or anything similair that I can look at? I have looked on the
doco site but there does not seem to be anything. Is there also some
documentation on how the architecture has changed between 8.xx and
10.xx I could have a read of?

Failing all of the above has anyone got any suggestions on how to do
the Indy 8.xx to 10.xx conversion with the least amount of pain? ;-)

TIA

-- 
--Donovan

3.TIdContext.Connection.ReadTimeout not work

AContext.Connection.IOHandler.ReadInteger not return after 25 ms.

********************************************************

function TIdTCPServer.DoExecute(AContext: TIdContext): Boolean;
begin
  AContext.Connection.IOHandler.ReadTimeout := 25;
  AContext.Connection.IOHandler.ReadInteger;
end;

********************************************************
I must use

        TIdIOHandlerStack(AContext.Connection.IOHandler).ReadTimeout := 25;

the readtimeout will work.


Must I use         TIdIOHandlerStack  to force ReadTimeout ??


4.ReadTimeout not working intermittently with TIdHTTPClient.Post

We've experienced some weird behavior on one of our systems that uses 
TIdHttpClient.Post (with SSL), in that once in a while, while a user's ISP 
is having connectivity issues, the ReadTimeout does not seem to work 
correctly, and a response is received after the timeout period.  My 
speculation is that the reply dribbles in, and that the ReadTimeout is 
satisfied when part of the reply is received, but the entire reply is not 
received until the timeout period has passed.  Example, timeout set to 45 
seconds, reply comes in at 80 seconds.  This caused us lots of problems 
because the timeout is built around a parent process with a longer timeout 
and we end up with systems that are out of sync.  The parent process 
thinking the first timed out and the first process with a valid (although 
late) reply.  Most of the time when we have a connectivity issue, the 
ReadTimeout works properly, just not always.

We are using Indy 9.0.14.  Other constraints - we have to use the Post 
method, SSL, and embed control characters in the request (All 3rd party 
constraints - not my choice!).

Thanks for any ideas or solutions tothis problem.

Doug


Here are relavant parts of the code:

MyHttpClient  := TIdHTTP.Create(MyhttpClient); //Create Indy Client Socket
MySSLIOHandler1 := TIdSSLIOHandlerSocket.Create(nil);
RequestTStringStream := TStringStream.Create(S);

MySSLIOHandler1.SSLOptions.Method := sslvSSLv23;
MyhttpClient.Port := 443;
MyhttpClient.IOHandler := IndySSLIOHandler1;
MyhttpClient.ReadTimeout := 4500;
MyhttpClient.CheckForDisconnect(False, True);

MyhttpClient.Request.CacheControl := 'no-cache';
MyhttpClient.HTTPOptions := [hoForceEncodeParams];
MyhttpClient.Request.ContentLength := Length(RequestString);

// had to use TStringStream cuz Indy will not remove ctrl characters with 
StringStream
RequestTStringStream.WriteString(RequestString);
try
  ReplyString := MyhttpClient.Post(HostAddress, RequestTStringStream);
except
  on EIdReadTimeout do
  begin
      // perform TimeOutReversal of transaction...
      // & other steps...
  end;
end; 


5.Indy 10: IdCoderTNEF.pas bug report

Team Indy,

The very useful IdCoderTNEF.pas appears to have a bug on line 1892:

  //LVal is now the days since 1/1/1601.  Subtract Delphi's 300-year
offset...
    Result := LVal;
  * Result := Result + StrToDate('01/01/1601');  {Do not localize} 

This does not work if your Windows date format is non-standard. Should
this not be?:

    Result := LVal;
    Result := Result + EncodeDate(1601, 1, 1);  {Do not localize}

Or, simply use -109205?


Regards,
Keith

6. Fix for DateTime Bug in Indy 10 in D2006

7. Bug Fix for Indy 9.0.14 - TIdPeerThread.Data destruction order

8. FIX BUG IE7 Address Bar Not Working



Return to delphi

 

Who is online

Users browsing this forum: No registered users and 78 guest