Apache Technologies 14 Bedienungsanleitung PDF herunterladen (Seite 54)

54 Chapter 3 Managing Websites

Default Content

The default content for the user’s Sites folder is an index.html file along with a few

images. It is important to note that this index.html file has text that describes the

Personal Web Sharing feature of Mac OS X client. The user should replace that

index.html file with one suited to the content of his or her Sites folder.

Accessing Web Content

Once the home directory is created, the content of the Sites folder within the user’s

home directory is visible whenever web service is running. If your server is named

example.com and the user’s short name is refuser, the content of the Sites folder can be

accessed at the URL http://example.com/~refuser.

If the user has multiple short names, any of those can also be used after the tilde to

access that same content.

If the user has placed a content file named foo.html in his or her Sites folder, that file

should be available at http://example.com/~refuser/foo.html.

If the user has placed multiple content files in his or her Sites folder, and cannot modify

the index.html to include links to those files, the user may benefit from the automatic

folder indexing described previously. If the “Enable folder listing” setting is enabled, an

index listing of file names will be visible to browsers at http://example.com/~refuser.

Indexing settings also apply to subfolders placed in the user’s Sites folder. If the user

adds a content subfolder named Example to the Sites folder, and either an index.html

file is present inside the Example folder, or folder indexing is enabled for that user’s site,

then the folder will be available to browsers at http://example.com/~refuser/Example.

The Module mod_hfs_apple Protects Web Content Against Case Insensitivity

in the HFS File System

Mac OS X Server version 10.4 provides case-sensitive coverage for HFS file names. This

feature should mean that the extra protection of mod_hfs_apple (discussed below) is

not necessary.

The HFS Extended volume format commonly used for Mac OS X Server preserves the

case of file names but does not distinguish between a file or folder named “Example”

and one named “eXaMpLe.” Were it not for mod_hfs_apple, this would be a potential

issue when your web content resides on such a volume and you are attempting to

restrict access to all or part of your web content using security realms. If you set up a

security realm requiring browsers to use a name and a password for read-only access to

content within a folder named “Protected,” browsers would need to authenticate in

order to access the following URLs:

http://example.com/Protected

http://example.com/Protected/secret

1 2 ... 49 50 51 52 53 54 55 56 57 58 59 ... 82 83

Keine Kommentare

Apache Technologies 14 Bedienungsanleitung Seite 54