Mailing List Archive

unsuscribe
> -----Mensaje original-----
> De: Rich Bowen [SMTP:rbowen@rcbowen.com]
> Enviado el: Lunes, 28 de Agosto de 2000 21:29
> Para: apache-docs@apache.org
> Asunto: Re: Patch: (Docs) VirtualHost
>
> Rich Bowen wrote:
> >
> > Here's something similar to what I submitted a while ago, but in more
> > detail, for the Virtual Host section of the documentation, the examples
> > document:
>
> Bah. I'm sorry. Here it is without the screwed-up formatting and missing
> close tags.
>
> [rbowen@buglet vhosts]$ cvs diff -u examples.html
> Index: examples.html
> ===================================================================
> RCS file:
> /home/cvspublic/httpd-docs-1.3/htdocs/manual/vhosts/examples.html,v
> retrieving revision 1.5
> diff -u -r1.5 examples.html
> --- examples.html 1998/09/17 14:15:02 1.5
> +++ examples.html 2000/08/29 02:27:43
> @@ -224,6 +224,39 @@
> <SAMP>111.22.33.55</SAMP> with an unknown or no <CODE>Host:</CODE>
> header will be served from <SAMP>www.otherdomain.tld</SAMP>.
> </BLOCKQUOTE>
> +
> +<LI><STRONG>Setup 3:</STRONG>
> + The server machine has two IP addresses
> (<SAMP>192.168.1.1</SAMP>
> + and <SAMP>111.22.33.55</SAMP>). The machine is sitting between
> + an internal (intranet) network and an external (internet)
> network.
> + Outside of the network, the name <SAMP>server1.domain.tld</SAMP>
> + resolves to the external address (<SAMP>111.22.33.55</SAMP>),
> but
> + inside the network, that same name resolves to the internal
> + address (<SAMP>192.168.1.1</SAMP>).<P>
> +
> + The server can be made to respond to internal and external
> + requests with the same content, with just one
> <CODE>VirtualHost</CODE>
> + section.
> + <P>
> +
> + <STRONG>Server configuration:</STRONG>
> +
> + <BLOCKQUOTE><PRE>
> + ...
> + NameVirtualHost 192.168.1.1
> + NameVirtualHost 111.22.33.55
> +
> + &lt;VirtualHost 192.168.1.1 111.22.33.55&gt;
> + DocumentRoot /www/server1
> + ServerName server1.domain.tld
> + ServerAlias server1
> + ...
> + &lt;/VirtualHost&gt;
> + </PRE></BLOCKQUOTE>
> +
> + Now requests from both networks will be served from the same
> + <CODE>VirtualHost</CODE>
> +
> </UL>
>
> <HR>
>
> --
> rbowen@rcbowen.com
> Come hear me at ApacheCon! - http://www.apachecon.com/
> Author - Apache Server Unleashed - http://apacheunleashed.com/
Re: unsuscribe [ In reply to ]
unsuscribe


Joshua Slive a écrit :

> As I think is evident, I am interested in improving the consistency (and
> usability) of the module docs by putting them all in a standard format. I
> have made a suggestion of a format (See message-id
> <Pine.SOL.4.20.0009141601450.19470-300000@garibaldi.commerce.ubc.ca>)
> but I really don't feel comfortable going ahead without some feedback.
> I am sure that there are improvements that could be made, since I am
> neither an HTML design expert, nor a documentation expert.
>
> So, how about some of you lurkers out there on the list take a look and
> make some suggestions. (Feedback from Apache group members is obviously
> acceptable as well.)
>
> The format I suggested is just about as close as possible to the format
> that many of the module docs are already in. Is more detail needed? Less
> detail? Should we be looking at a non-html format (DocBook, XML,
> whatever...). Should it be "flashier" like mod_rewrite.html?
>
> --
> Joshua Slive
> slive@finance.commerce.ubc.ca
> http://finance.commerce.ubc.ca/~slive/
> Phone: (604) 822-1871
Re: unsuscribe [ In reply to ]
----- Original Message -----
From: "Régis Kla" <kla@univ-paris1.fr>
To: <apache-docs@apache.org>
Sent: Tuesday, October 10, 2000 11:19 AM
Subject: Re: unsuscribe


> unsuscribe
>
>
> Joshua Slive a écrit :
>
> > As I think is evident, I am interested in improving the consistency (and
> > usability) of the module docs by putting them all in a standard format.
I
> > have made a suggestion of a format (See message-id
> > <Pine.SOL.4.20.0009141601450.19470-300000@garibaldi.commerce.ubc.ca>)
> > but I really don't feel comfortable going ahead without some feedback.
> > I am sure that there are improvements that could be made, since I am
> > neither an HTML design expert, nor a documentation expert.
> >
> > So, how about some of you lurkers out there on the list take a look and
> > make some suggestions. (Feedback from Apache group members is obviously
> > acceptable as well.)
> >
> > The format I suggested is just about as close as possible to the format
> > that many of the module docs are already in. Is more detail needed?
Less
> > detail? Should we be looking at a non-html format (DocBook, XML,
> > whatever...). Should it be "flashier" like mod_rewrite.html?
> >
> > --
> > Joshua Slive
> > slive@finance.commerce.ubc.ca
> > http://finance.commerce.ubc.ca/~slive/
> > Phone: (604) 822-1871
>