🚀 go-pugleaf

Hi again Remy, see what happens when you do not know what you are doing, 
I did not realize that the Keep-Alive Directive was coming from the 
browser and being sent to the WebServer via my code, like you said I 
tweaked the header to remove this directive so the connection is now 
non-pesistant and the code block.......

       TMemoryStream * Stream = new TMemoryStream;
       WebSite->ReadStream(Stream, -1, true);
       Browser->Connection->WriteStream(Stream);
       delete Stream;

works perfectly, since the webserver will not make persistant connections.

Here is a snap of the headers.......

GET 
http://tothechildren.tripod.com/imagelib/sitebuilder/layout/nature_s_b2.gif 
HTTP/1.0
Accept: */*
Referer: http://tothechildren.tripod.com/childrenstories/id5.html
Accept-Language: en-tt
Proxy-Connection: Keep-Alive
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; 
MathPlayer 2.0; .NET CLR 1.1.4322)
Host: tothechildren.tripod.com
Cookie: CookieStatus=COOKIE_OK; 
MEMBER_PAGE=tothechildren/childrenstories/id5.html; 
REFERRER=http://images.google.com/imgres?imgurl=http://tothechildren.tripod.com/sitebuildercontent/sitebuilderpictures/ashley.jpg&imgrefurl=http://tothechildren.tripod.com/childrenstories/id5.html&h=731&w=1041&sz=894&tbnid=UV26nB6GTP0J:&tbnh=105&tbnw=149&start=6&prev=/images%3Fq%3Dbig%2Bold%2Bshoe%26hl%3Den%26lr%3D%26sa%3DN; 
sidebarurl=http://tothechildren.tripod.com/childrenstories/id5.html


As you can see I am not sending the "Proxy-Connection: Keep-Alive" to 
the server so things are near perfect, Now I just have to handle 
exception errors (yeah 'just') and other error handling stuff and I will 
have a nifty proxy server. I am using this to do content filtering.

Thanks for your help...