[EMAIL PROTECTED] wrote:
> 
> Well, like i said, i wrote the server from the port access level up. What
> header would Rebol like, and how is it sent?
> 

I don't work at REBOL (and I don't play one on TV... ;-), but I have
played around a little with bare-knuckled HTTP.  My experience is that
different browsers have different levels of tolerance to servers (or
web pages) that don't follow the standards.  If you're running against
a home-grown HTTP server, I'd suggest that you try to make sure your
server is returning all of the most common headers.  There are two
good ways to find out what they are:

1) Use telnet to connect to a commercial server at port 80.  A typical
   such manual connection looks something like the following. The "->"
   and "<-" prefixes show which lines I typed and which ones the server
   sent back; they're NOT part of the actual data.  Server names have
   been changed to protect the innocent.  ;-)

   -> telnet x.y.z.com 80
   <- Trying...
   <- Connected to x.y.z.com.
   <- Escape character is '^]'.
   -> GET /tiny.html HTTP/1.0
   -> 
   <- HTTP/1.1 200 OK
   <- Server: Netscape-Enterprise/3.6
   <- Date: Thu, 04 Nov 1999 14:22:30 GMT
   <- Content-type: text/html
   <- Connection: close
   <- 
   <- <html>
   <- <head><title>Hi!</title></head>
   <- <body><h1>Hi!</h1></body>
   <- </html>
   <- 
   <- Connection closed by foreign host.

   (I'm back to the command line prompt at this point.)

   You might try simply faking the above headers (including the
   blank line) and see if that helps.  Those should be adequate,
   as the following REBOL snippet implies:

      >> read http://x.y.z.com/tiny.html
      == {<html>
      <head><title>Hi!</title></head>
      <body><h1>Hi!</h1></body>
      </html>

      }
      >> 

2) If the problem really is related to HTTP protocol compliance,
   you might want to look at the O'Reilly book

      _Web_Client_Programming_with_Perl_
      Clinton Wong, 1997
      ISBN 1-56592-214-x

   Even though the book uses The Wrong Language ;-) , the first
   three chapters provide the best narrative explanation of HTTP
   client-server interactions I've seen, and Appendix A contains
   a detailed explanation of HTTP header content and meaning.

Good Luck!

-jn-

Reply via email to