From f40d338fa281044eb17a5d6f06e987909972fdba Mon Sep 17 00:00:00 2001 From: eknauel Date: Wed, 2 Jun 2004 14:26:03 +0000 Subject: [PATCH] + enforce coporate identity, it's SUnet not SUNet. + fixed typos --- doc/latex/httpd.tex | 12 ++++++------ 1 file changed, 6 insertions(+), 6 deletions(-) diff --git a/doc/latex/httpd.tex b/doc/latex/httpd.tex index 579a0e2..bbb424f 100644 --- a/doc/latex/httpd.tex +++ b/doc/latex/httpd.tex @@ -164,7 +164,7 @@ dissect requests are defined in the \texttt{httpd-requests} structure: representing the version specified in the HTTP request. \ex{Request-headers} returns an association lists of header field names and their values, each represented by a list of strings, one - for each line. \ex{Request-socket} returns the the socket connected + for each line. \ex{Request-socket} returns the socket connected to the client.\footnote{Request handlers should not perform I/O on the request record's socket. Request handlers are frequently called recursively, and doing I/O directly to the socket might bypass a @@ -685,15 +685,15 @@ parse these strings. Network traffic with a HTTP server is usually encrypted and protected from manipulation using the cryptographic algorithm provided by an implementation of the \textit{secure socket layer}, SSL for short. -SUNet does not have support for SSL yet. However, an Apache +SUnet does not have support for SSL yet. However, an Apache web-server with SSL support can be configured as a proxy. In this setup the Apache web-server accepts encrypted requests and forwards -them to a SUNet web-server running locally. This section describes +them to a SUnet web-server running locally. This section describes how to set up Apache as an encrypting proxy, assuming the reader has basic knowledge about Apache and its configuration directives. The following excerpt shows a minimalist SSL virtual host that -forwards requests to a SUNet server. +forwards requests to a SUet server. \begin{alltt} @@ -719,7 +719,7 @@ virtual host listens for incoming connections on port 443, which is the standard port for encrypted HTTP traffic. \texttt{SSLRequireSSL} ensures that server accepts encrypted connections only. -In terms of the Apache documentation, the the web-server acts as a so +In terms of the Apache documentation, the web-server acts as a so called \textit{reverse proxy}. The option \texttt{ProxyRequests} has a misleading name. Setting this option to off does only turns off Apache's facility to act as a \textit{forward proxy} and has no effect @@ -728,7 +728,7 @@ turning on \texttt{ProxyRequests} is dangerous, because this turns Apache into a proxy server that can be used from anywhere to access any site that is accessible to the Apache server. -In this setting, all requests get forwarded to a SUNet web-server +In this setting, all requests get forwarded to a SUnet web-server which listens for incoming connections on localhost port 8080 only, thus, it is not reachable from a remote machine. Apache forwards all requests to the host and port specified by the \texttt{ProxyPass}