home *** CD-ROM | disk | FTP | other *** search
- <html><head><title>ArcWebTCP -- the Acorn TCP/IP fetcher for ArcWeb</title>
- </head><body><h1><img src="#!arcwebtcp">ArcWebTCP</h1>
-
- ArcWebTCP is a fetching tool for ArcWeb. It handles the fetching via a
- variety of different methods, all over the Acorn TCP/IP release 2 BSD
- sockets interface. The InetDB
- module supplied with FreeNet can provide the DNS resolver. You need access to
- a suitable DNS server. Your network provider will be able to tell you what
- DNS servers to configure into InetDB.
- Since ArcWebTCP uses only the socket level
- interface provided by Acorn TCP/IP, it will also run over anything else
- which provides an identical SWI interface (chunk &41200).
-
- ArcWebTCP supports<ul>
- <li>HTTP (HyperText Transfer Protocol)
- <li>FTP (File Transfer Protocol)
- <li>SMTP (Simple Mail Transfer Protocol
- <li>NNTP (Network News Transfer Protocol)
- <li>Finger
- <li>Telnet
- <li>Gopher
- <li>WAIS
-
- </ul>although WAIS
- is achieved through the use of proxy
- services such as those available at wwwcache.hensa.ac.uk. ArcWebTCP talks
- HTTP to proxy servers which perform the interaction with the remote site and
- send back the result via the HTTP protocol. Non-documents (eg. WAIS
- menus) are returned as HTML documents generated by the proxy server. Proxy
- servers are useful things to run on firewall machines as it allows people
- inside the firewall to access the Web services.<p>
- Other facilities supported by <bf>ArcWebTCP</bf> include<ul>
-
- <li>Transparent handling of <em>Location</em> indicating that a document has
- moved. The redirection is detected whilst the original response is being
- read and the query replaced by a request for the new URL. Note that if a
- failure occurs whilst fetching the replacement URL, any errors reported will
- be reported as having come from the original document requested and not the
- resultant of the search. There is no limit to the number of
- <em>Location</em> directives that may be chained together, ArcWebTCP will
- continue following the trail until the answer is found
-
- <li>Allows <em>manual</em> proxying. If you specify a URL such as:
- <em>http://someproxy.somedomain/gopher://doc.ic.ac.uk/</em> then this would
- be treated as a proxy request to retrieve the top level gopher menu from
- doc.ic.ac.uk. Note that in this case, if HTTP proxying has been enabled,
- then the request may be further transformed by <bf>ArcWebTCP</bf> into
- <em>http://wwwcache.hensa.ac.uk:8080/http://someproxy.somedomain/gopher://doc.ic.ac.uk</em>
- giving a two stage proxy, which is perfectly valid.
-
- </ul>
-
-
- <h3>Testing your Configuration</h3>
-
- You can test the configuration of the nameservers by using the dialogue
- boxes accessed via the <img src="#!arcwebtcp" alt="ArcWebTCP icon bar icon">
- menu. You can look up hosts by name or by IP address. For the former,
- enter the hostname in the top icon and press RETURN. The IP address will be
- looked up and the result placed in the lower icon. The latter performs the
- reverse lookup, so enter the IP address in the top icon and press RETURN
- and the result of the reverse lookup is placed in the lower icon.<p>
- Try looking up your own hostname, and then another machine in your domain,
- then try giving the fully qualified name of a machine in your domain, and
- then a remote machine. eg. I can test by looking up the following hosts:
- delenn, dsse, delenn.ecs.soton.ac.uk, www.hensa.ac.uk.
-
- <hr> </body><address><a
- href="http://www.dsse.ecs.soton.ac.uk/">S.N.Brodie</a><br> Department of
- Electronics & Computer Science<br> University of
- Southampton</address></html>
-