🚀 go-pugleaf

Hi Hans

OK. The headers that I get returned are below. I have tried adding the
missing headers but still get the same problem. However, in playing around
with the links, I find that if I refer to the remote file with a relative
path (i.e. href="test4.htm") then everything works fine, whereas if I refer
to it with an absolute path (i.e. href=http://machine/path/test4.htm) I get
the same problem. This is also true for the cgi I am calling. This is now
starting to look like it is not a Borland problem but more likely a
Microsoft problem. I have solved the problem by converting all my links to
relative links and everything is working fine.

I am still interested in an explanation if you or anyone else can give one,
but since the immediate problem is solved I would not wish anyone to waste
time on my behalf.

Thank you for your help in this - I have learnt a lot and while the solution
was not directly related to your suggestions, I doubt that I would have got
there without them

Cheers

Gordon



*************** From TWebResponse ***************
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.1
Date: Thu, 24 Feb 2005 14:27:52 GMT
Content-Type: text/html
Title: Test
Content-Length: 44739
Content:




*************** From direct call ***************
HTTP/1.1 200 OK
Server: Microsoft-IIS/5.1
Date: Thu, 24 Feb 2005 14:31:20 GMT
Content-Type: text/html
Accept-Ranges: bytes
Last-Modified: Thu, 24 Feb 2005 13:38:12 GMT
ETag: "0ba8d15761ac51:a81"
Content-Length: 44739




"Hans Galema" <notused@notused.nl> wrote in message
news:421ddcf7$1@newsgroups.borland.com...
> Gordon Dooley wrote:
>
> > It appears that it is only scenario 1 that causes the problem.
>
> You could write a separate app using TIdHTTP or TNMHTTP
> to get both the static page from the webserver and the one
> produced by TWebResponse. Then compare the headers.
>
> The exampleproject that comes with builder for TNMHTTP can do
> that. So you could immediately use it.
>
> Hans.