----- Original Message -----
From: <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, November 03, 1999 6:53 AM
Subject: [REBOL] http server... Re:(4)
> Hi Kat,
>
> Ok, well, from this post you seem to have the direction of slashes down
now.
My server accepts the slashes in both directions, serving the requested file
either way. The direction is only important to the dns resolution, not the
file requested.
> Why the properly formed URL still hangs the 'read command I cannot say,
> since 'read is native and I am not privy to its code or why the error
> message is appearing.
>
> However, in your earlier example, the explanation of why the server times
> out on the 'read from rebol is cuz rebol stops running when it encounters
a
> script error or some kind while reading the URL. From that point on rebol
> is dead in the water, nothing more is accepted, and eventually the server
> sees the lack of response from rebol and kills the connection.
>
> Why rebol is choking is still a mystery to me. I would still suggest you
> try the very simple HTML code I recommended in my last post. Simply
> cut/paste them to some .html file and attempt to read them. By
simplifying
> the problem considerably, perhaps we can sneak up on what is causing rebol
> to choke. As you point out, obviously rebol reads pages off the web
> (probably the same ones you copy to your system), others can read your
pages
> via your server... so there's got to be something in what your server is
> passing that rebol is not expecting.
file test1 :
<HTML><HEAD></HEAD><BODY>TEST</BODY><HTML>
file test2:
<HTML>
<HEAD></HEAD>
<BODY>
TEST
</BODY>
</HTML>
Ok, i did the
http://localhost/test1.txt
and
http://localhost/test2.txt
in IE5 and both files displayed properly.
Rebol did this:
>> print read http://localhost/test1.txt
connecting to: localhost
** Script Error: Out of range or past end.
** Where: either none? result: select response-actions
>>
>> print read http://localhost/test2.txt
connecting to: localhost
** Script Error: Out of range or past end.
** Where: either none? result: select response-actions
>>
> Hmmm... I'm wondering about rebol's read buffer size... i notice that the
> file you were trying to read (in last post example) was 185k bytes. Try
the
> short, simple file I suggested... if it chokes on that, then it's got to
be
> something specific to what your server is passing back.
It also chokes on 200byte files. and on those two 50byte files above. What
is Rebol requiring that IE5 and the other browsers don't care about?
Kat
