Skip to Content.
Sympa Menu

baslinux - Re: [BL] httpd

baslinux AT lists.ibiblio.org

Subject: Baslinux mailing list

List archive

Chronological Thread  
  • From: 3aoo-cvfd AT dea.spamcon.org
  • To: baslinux AT lists.ibiblio.org
  • Subject: Re: [BL] httpd
  • Date: Tue, 2 Nov 2004 07:34:23 +1300

Stephen Clement wrote:
>
> Any idea what version it is then?

I think it's version 1.34.

> >> I can't get anything else no matter what I specify
> >> in my httpd.conf. Any ideas?

----------------------------------------------------------------
Typical usage:
for non root user
httpd -p 8080 -h $HOME/public_html
or for daemon start from rc script with uid=0:
httpd -u www
This is equivalent if www user have uid=80 to
httpd -p 80 -u 80 -h /www -c /etc/httpd.conf -r "Web Server Authentication"

When a url contains "cgi-bin" it is assumed to be a cgi script. The
server changes directory to the location of the script and executes it
after setting QUERY_STRING and other environment variables.

The server can also be invoked as a url arg decoder and html text encoder
as follows:
foo=`httpd -d $foo` # decode "Hello%20World" as "Hello World"
bar=`httpd -e "<Hello World>"` # encode as "&#60Hello&#32World&#62"
Note that url encoding for arguments is not the same as html encoding for
presenation. -d decodes a url-encoded argument while -e encodes in html
for page display.

-----------------------------------
httpd.conf has the following format:
-----------------------------------
A:172.20. # Allow address from 172.20.0.0/16
A:10.0.0.0/25 # Allow any address from 10.0.0.0-10.0.0.127
A:10.0.0.0/255.255.255.128 # Allow any address that previous set
A:127.0.0.1 # Allow local loopback connections
D:* # Deny from other IP connections
/cgi-bin:foo:bar # Require user foo, pwd bar on urls starting with /cgi-bin/
/adm:admin:setup # Require user admin, pwd setup on urls starting with /adm/
/adm:toor:PaSsWd # or user toor, pwd PaSsWd on urls starting with /adm/
.au:audio/basic # additional mime type for audio.au files

A/D may be as a/d or allow/deny - first char case unsensitive
Deny IP rules take precedence over allow rules.

The Deny/Allow IP logic:
- Default is to allow all. No addresses are denied unless
denied with a D: rule.
- Order of Deny/Allow rules is significant
- Deny rules take precedence over allow rules.
- If a deny all rule (D:*) is used it acts as a catch-all for unmatched
addresses.
- Specification of Allow all (A:*) is a no-op

Example:
1. Allow only specified addresses
A:172.20 # Allow any address that begins with 172.20.
A:10.10. # Allow any address that begins with 10.10.
A:127.0.0.1 # Allow local loopback connections
D:* # Deny from other IP connections

2. Only deny specified addresses
D:1.2.3. # deny from 1.2.3.0 - 1.2.3.255
D:2.3.4. # deny from 2.3.4.0 - 2.3.4.255
A:* # (optional line added for clarity)

If a sub directory contains a config file it is parsed and merged with
any existing settings as if it was appended to the original configuration.

subdir paths are relative to the containing subdir and thus cannot
affect the parent rules.

Note that since the sub dir is parsed in the forked thread servicing
the subdir http request, any merge is discarded when the process exits.
As a result, the subdir settings only have a lifetime of a single request.

If -c is not set, an attempt will be made to open the default
root configuration file. If -c is set and the file is not found,
the server exits with an error.
-------------------------------------------------------------------


Cheers,
Steven

____________________________
http://www.basiclinux.com.ru




Archive powered by MHonArc 2.6.24.

Top of Page