Hi, I have a CGI program that serves some files using this code in an action:

AResponse.ContentStream := TFileStream.Create(lImagePath, fmOpenRead);

The problem I'm facing is that some times the client breaks the connection to the server, aparently leaving the file open. If the client tries to download the file again, a code 500 is returned.

Is there a way to detect the connection break and destroy the stream gracefully?.

Regards,

2014-07-03 16:51 GMT-03:00 Leonardo M. Ram? :

You can use the FreeContentStream property and free your stream manually, e.g.:

var
  f: TFileStream;
begin
  f := TFileStream.Create(...);
  try
    HttpResponse.FreeContentStream := False;
    HttpResponse.ContentType := 'application/octet-stream';
    HttpResponse.ContentStream := f;
    HttpResponse.SendContent;
  finally
    f.Free;
  end;
end;

Thanks Silvio, it seems to work.

Mmm, no, too fast.

Maybe the problem is on the client side. I'm using Synapse library as client, and I'm issuing THttpSend's Abort method to stop downloading. Is the cgi notified when the client does an Abort call?.

2014-07-03 17:33 GMT-03:00 Leonardo M. Ram? :
[...]

Mmm, no, too fast. Maybe the problem is on the client side. I'm using Synapse library as client, and I'm issuing THttpSend's Abort method to stop downloading.

You can change your 'broker' to a embedded HTTP server, and put a break point and debug both (client/server).

Is the cgi notified when the client does an Abort call?.

Hm... AFAIK, no.

Indeed. The CGI program is just terminated.

Normally the file stream is then closed by the OS, so this should not have any side effects. (unless the OS is buggy).

If you do observe side effects, try opening the file without share locks. using flags (fmOpenRead or fmShareDenyNone), I think.

Michael.

Thanks Michael, using (fmOpenRead or fmShareDenyNone) params did the trick!.

Regards,

On what platform did you get this ?

Michael