PDA

Archiv verlassen und diese Seite im Standarddesign anzeigen : Alias beim apache will einfach nicht funktionieren



smiler
29.10.02, 10:02
Hallo Gemeinde,
Ich fuerchte fast, ich werde zu Stammgast hier. Und dann auch noch mit solchem "Pippifax" :-(
O.K. lange Einleitung kuzer Sinn...
Ich versuche hier auf Arbeit krampfhaft einen Aliaseintrag in die httpd.conf des apaches einzutragen, aber irgendwie bekommen ich immer wieder beim versuchten Zugriff auf die entsprechende Seite einen "403 forbidden". Und ich bin langsam wirklich ratlos.
Ich habe es gestern abend mal testweise zu Hause probiert (da laeuft eine suse8.0) und es ging wirklich problemlos. Und hier auf Arbeit? argh, manchmal fuehle ich mich wirklich wie das erste mal am rechner, furchtbar. Irgendwie sehe ich denn Wald vor lauter Baeumen nicht. Evtl. koennte mal jemand schauen, vielleicht findet er den Fehler?
Also, die entsprechenden Files, die der Nutzer jasonk in seinem homeverzeichnis jasonk in "www/html" ablegt sollen auf dem Server unter www.blahblah.com/interweb sichtbar sein.
siehe die settings im alias-part.
Eventuell/Wahrscheinlich(?) liegt es an den Filepermissions. aber da habe ich die soweit angepasst, wie es in den anderen vom Webserver zugreibaren Verzeichnissen aussieht.
Wo ist mein Fehler?


Vielen Dank Smiler

(kann man abchecken, ob mod_alias ueberhaupt "anspringt", oder wuerde das beim Serverstart schon einen Fehler geben?)

hier kommt die httpd.conf (hoffentlich nicht zu lang fuer das Forum):

##
## httpd.conf -- Apache HTTP server configuration file
##

#
# Based upon the NCSA server configuration files originally by Rob McCool.
#
# This is the main Apache server configuration file. It contains the
# configuration directives that give the server its instructions.
# See <URL:http://www.apache.org/docs/> for detailed information about
# the directives.
#
# Do NOT simply read the instructions in here without understanding
# what they do. They're here only as hints or reminders. If you are unsure
# consult the online docs. You have been warned.
#
# After this file is processed, the server will look for and process
# /usr/local/apache/conf/srm.conf and then /usr/local/apache/conf/access.conf
# unless you have overridden these with ResourceConfig and/or
# AccessConfig directives here.
#
# The configuration directives are grouped into three basic sections:
# 1. Directives that control the operation of the Apache server process as a
# whole (the 'global environment').
# 2. Directives that define the parameters of the 'main' or 'default' server,
# which responds to requests that aren't handled by a virtual host.
# These directives also provide default values for the settings
# of all virtual hosts.
# 3. Settings for virtual hosts, which allow Web requests to be sent to
# different IP addresses or hostnames and have them handled by the
# same Apache server process.
#
# Configuration and logfile names: If the filenames you specify for many
# of the server's control files begin with "/" (or "drive:/" for Win32), the
# server will use that explicit path. If the filenames do *not* begin
# with "/", the value of ServerRoot is prepended -- so "logs/foo.log"
# with ServerRoot set to "/usr/local/apache" will be interpreted by the
# server as "/usr/local/apache/logs/foo.log".
#

### Section 1: Global Environment
#
# The directives in this section affect the overall operation of Apache,
# such as the number of concurrent requests it can handle or where it
# can find its configuration files.
#

#
# ServerType is either inetd, or standalone. Inetd mode is only supported on
# Unix platforms.
#
ServerType standalone

#
# ServerRoot: The top of the directory tree under which the server's
# configuration, error, and log files are kept.
#
# NOTE! If you intend to place this on an NFS (or otherwise network)
# mounted filesystem then please read the LockFile documentation
# (available at <URL:http://www.apache.org/docs/mod/core.html#lockfile>);
# you will save yourself a lot of trouble.
#
ServerRoot "/usr/local/apache"

#
# The LockFile directive sets the path to the lockfile used when Apache
# is compiled with either USE_FCNTL_SERIALIZED_ACCEPT or
# USE_FLOCK_SERIALIZED_ACCEPT. This directive should normally be left at
# its default value. The main reason for changing it is if the logs
# directory is NFS mounted, since the lockfile MUST BE STORED ON A LOCAL
# DISK. The PID of the main server process is automatically appended to
# the filename.
#
#LockFile /var/run/httpd.lock

#
# PidFile: The file in which the server should record its process
# identification number when it starts.
#
PidFile /var/run/httpd.pid

#
# ScoreBoardFile: File used to store internal server process information.
# Not all architectures require this. But if yours does (you'll know because
# this file will be created when you run Apache) then you *must* ensure that
# no two invocations of Apache share the same scoreboard file.
#
ScoreBoardFile /var/run/httpd.scoreboard

#
# In the standard configuration, the server will process httpd.conf (this
# file, specified by the -f command line option), srm.conf, and access.conf
# in that order. The latter two files are now distributed empty, as it is
# recommended that all directives be kept in a single file for simplicity.
# The commented-out values below are the built-in defaults. You can have the
# server ignore these files altogether by using "/dev/null" (for Unix) or
# "nul" (for Win32) for the arguments to the directives.
#
#ResourceConfig conf/srm.conf
#AccessConfig conf/access.conf

#
# Timeout: The number of seconds before receives and sends time out.
#
Timeout 300

#
# KeepAlive: Whether or not to allow persistent connections (more than
# one request per connection). Set to "Off" to deactivate.
#
KeepAlive On

#
# MaxKeepAliveRequests: The maximum number of requests to allow
# during a persistent connection. Set to 0 to allow an unlimited amount.
# We recommend you leave this number high, for maximum performance.
#
MaxKeepAliveRequests 100

#
# KeepAliveTimeout: Number of seconds to wait for the next request from the
# same client on the same connection.
#
KeepAliveTimeout 15

#
# Server-pool size regulation. Rather than making you guess how many
# server processes you need, Apache dynamically adapts to the load it
# sees --- that is, it tries to maintain enough server processes to
# handle the current load, plus a few spare servers to handle transient
# load spikes (e.g., multiple simultaneous requests from a single
# Netscape browser).
#
# It does this by periodically checking how many servers are waiting
# for a request. If there are fewer than MinSpareServers, it creates
# a new spare. If there are more than MaxSpareServers, some of the
# spares die off. The default values are probably OK for most sites.
#
MinSpareServers 5
MaxSpareServers 10

#
# Number of servers to start initially --- should be a reasonable ballpark
# figure.
#
StartServers 5

#
# Limit on total number of servers running, i.e., limit on the number
# of clients who can simultaneously connect --- if this limit is ever
# reached, clients will be LOCKED OUT, so it should NOT BE SET TOO LOW.
# It is intended mainly as a brake to keep a runaway server from taking
# the system with it as it spirals down...
#
MaxClients 150

#
# MaxRequestsPerChild: the number of requests each child process is
# allowed to process before the child dies. The child will exit so
# as to avoid problems after prolonged use when Apache (and maybe the
# libraries it uses) leak memory or other resources. On most systems, this
# isn't really needed, but a few (such as Solaris) do have notable leaks
# in the libraries. For these platforms, set to something like 10000
# or so; a setting of 0 means unlimited.
#
# NOTE: This value does not include keepalive requests after the initial
# request per connection. For example, if a child process handles
# an initial request and 10 subsequent "keptalive" requests, it
# would only count as 1 request towards this limit.
#
MaxRequestsPerChild 0

#
# Listen: Allows you to bind Apache to specific IP addresses and/or
# ports, in addition to the default. See also the <VirtualHost>
# directive.
#
#Listen 3000
#Listen 12.34.56.78:80

#
# BindAddress: You can support virtual hosts with this option. This directive
# is used to tell the server which IP address to listen to. It can either
# contain "*", an IP address, or a fully qualified Internet domain name.
# See also the <VirtualHost> and Listen directives.
#
#BindAddress *

#
# Dynamic Shared Object (DSO) Support
#
# To be able to use the functionality of a module which was built as a DSO you
# have to place corresponding `LoadModule' lines at this location so the
# directives contained in it are actually available _before_ they are used.
# Please read the file README.DSO in the Apache 1.3 distribution for more
# details about the DSO mechanism and run `httpd -l' for the list of already
# built-in (statically linked and thus always available) modules in your httpd
# binary.
#
# Note: The order in which modules are loaded is important. Don't change
# the order below without expert advice.
#
# Example:
# LoadModule foo_module libexec/mod_foo.so
LoadModule vhost_alias_module libexec/mod_vhost_alias.so
LoadModule env_module libexec/mod_env.so
LoadModule define_module libexec/mod_define.so
LoadModule config_log_module libexec/mod_log_config.so
LoadModule mime_magic_module libexec/mod_mime_magic.so
LoadModule mime_module libexec/mod_mime.so
LoadModule negotiation_module libexec/mod_negotiation.so
LoadModule status_module libexec/mod_status.so
LoadModule info_module libexec/mod_info.so
LoadModule includes_module libexec/mod_include.so
LoadModule autoindex_module libexec/mod_autoindex.so
LoadModule dir_module libexec/mod_dir.so
LoadModule cgi_module libexec/mod_cgi.so
LoadModule asis_module libexec/mod_asis.so
LoadModule imap_module libexec/mod_imap.so
LoadModule action_module libexec/mod_actions.so
LoadModule speling_module libexec/mod_speling.so
LoadModule userdir_module libexec/mod_userdir.so
LoadModule alias_module libexec/mod_alias.so
LoadModule rewrite_module libexec/mod_rewrite.so
LoadModule access_module libexec/mod_access.so
LoadModule auth_module libexec/mod_auth.so
LoadModule anon_auth_module libexec/mod_auth_anon.so
LoadModule dbm_auth_module libexec/mod_auth_dbm.so
LoadModule digest_module libexec/mod_digest.so
LoadModule proxy_module libexec/libproxy.so
LoadModule cern_meta_module libexec/mod_cern_meta.so
LoadModule expires_module libexec/mod_expires.so
LoadModule headers_module libexec/mod_headers.so
LoadModule usertrack_module libexec/mod_usertrack.so
LoadModule unique_id_module libexec/mod_unique_id.so
LoadModule setenvif_module libexec/mod_setenvif.so
<IfDefine SSL>
LoadModule ssl_module libexec/libssl.so
</IfDefine>

# Reconstruction of the complete module list from all available modules
# (static and shared ones) to achieve correct module execution order.
# [WHENEVER YOU CHANGE THE LOADMODULE SECTION ABOVE UPDATE THIS, TOO]
ClearModuleList
AddModule mod_vhost_alias.c
AddModule mod_env.c
AddModule mod_define.c
AddModule mod_log_config.c
AddModule mod_mime_magic.c
AddModule mod_mime.c
AddModule mod_negotiation.c
AddModule mod_status.c
AddModule mod_info.c
AddModule mod_include.c
AddModule mod_autoindex.c
AddModule mod_dir.c
AddModule mod_cgi.c
AddModule mod_asis.c
AddModule mod_imap.c
AddModule mod_actions.c
AddModule mod_speling.c
AddModule mod_userdir.c
AddModule mod_alias.c
AddModule mod_rewrite.c
AddModule mod_access.c
AddModule mod_auth.c
AddModule mod_auth_anon.c
AddModule mod_auth_dbm.c
AddModule mod_digest.c
AddModule mod_proxy.c
AddModule mod_cern_meta.c
AddModule mod_expires.c
AddModule mod_headers.c
AddModule mod_usertrack.c
AddModule mod_unique_id.c
AddModule mod_so.c
AddModule mod_setenvif.c
<IfDefine SSL>
AddModule mod_ssl.c
</IfDefine>

#
# ExtendedStatus controls whether Apache will generate "full" status
# information (ExtendedStatus On) or just basic information (ExtendedStatus
# Off) when the "server-status" handler is called. The default is Off.
#
#ExtendedStatus On

### Section 2: 'Main' server configuration
#
# The directives in this section set up the values used by the 'main'
# server, which responds to any requests that aren't handled by a
# <VirtualHost> definition. These values also provide defaults for
# any <VirtualHost> containers you may define later in the file.
#
# All of these directives may appear inside <VirtualHost> containers,
# in which case these default settings will be overridden for the
# virtual host being defined.
#

#
# If your ServerType directive (set earlier in the 'Global Environment'
# section) is set to "inetd", the next few directives don't have any
# effect since their settings are defined by the inetd configuration.
# Skip ahead to the ServerAdmin directive.
#

#
# Port: The port to which the standalone server listens. For
# ports < 1023, you will need httpd to be run as root initially.
#
Port 80

##
## SSL Support
##
## When we also provide SSL we have to listen to the
## standard HTTP port (see above) and to the HTTPS port
##
<IfDefine SSL>
Listen 80
Listen 443
</IfDefine>

#
# If you wish httpd to run as a different user or group, you must run
# httpd as root initially and it will switch.
#
# User/Group: The name (or #number) of the user/group to run httpd as.
# . On SCO (ODT 3) use "User nouser" and "Group nogroup".
# . On HPUX you may not be able to use shared memory as nobody, and the
# suggested workaround is to create a user www and use that user.
# NOTE that some kernels refuse to setgid(Group) or semctl(IPC_SET)
# when the value of (unsigned)Group is above 60000;
# don't use Group nobody on these systems!
#
User "#48"
Group "#48"

#
# ServerAdmin: Your address, where problems with the server should be
# e-mailed. This address appears on some server-generated pages, such
# as error documents.
#
ServerAdmin xxxx@xxxxxxxxxxxxxx

#
# ServerName allows you to set a host name which is sent back to clients for
# your server if it's different than the one the program would get (i.e., use
# "www" instead of the host's real name).
#
# Note: You cannot just invent host names and hope they work. The name you
# define here must be a valid DNS name for your host. If you don't understand
# this, ask your network administrator.
# If your host doesn't have a registered DNS name, enter its IP address here.
# You will have to access it by its address (e.g., http://123.45.67.89/)
# anyway, and this will make redirections work in a sensible way.
#
# 127.0.0.1 is the TCP/IP local loop-back address, often named localhost. Your
# machine always knows itself by this address. If you use Apache strictly for
# local testing and development, you may use 127.0.0.1 as the server name.
#
#ServerName localhost.localdomain

#
# DocumentRoot: The directory out of which you will serve your
# documents. By default, all requests are taken from this directory, but
# symbolic links and aliases may be used to point to other locations.
#
DocumentRoot "/home/scottweb/www/html"

#
# Each directory to which Apache has access, can be configured with respect
# to which services and features are allowed and/or disabled in that
# directory (and its subdirectories).
#
# First, we configure the "default" to be a very restrictive set of
# permissions.
#
<Directory />
Options FollowSymLinks
AllowOverride All
</Directory>

#
# Note that from this point forward you must specifically allow
# particular features to be enabled - so if something's not working as
# you might expect, make sure that you have specifically enabled it
# below.
#

#
# This should be changed to whatever you set DocumentRoot to.
#
<Directory "/home/scottweb/www/html">

#
# This may also be "None", "All", or any combination of "Indexes",
# "Includes", "FollowSymLinks", "ExecCGI", or "MultiViews".
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
Options FollowSymLinks MultiViews

# For time of development the access is restricted

#
# This controls which options the .htaccess files in directories can
# override. Can also be "All", or any combination of "Options", "FileInfo",
# "AuthConfig", and "Limit"
#
AllowOverride All

#
# Controls who can get stuff from this server.
#
Order allow,deny
Allow from all
</Directory>



#
# DirectoryIndex: Name of the file or files to use as a pre-written HTML
# directory index. Separate multiple entries with spaces.
#
<IfModule mod_dir.c>
DirectoryIndex index.html index.jsp index.xtp
</IfModule>

#
# AccessFileName: The name of the file to look for in each directory
# for access control information.
#
AccessFileName .htaccess

#
# The following lines prevent .htaccess files from being viewed by
# Web clients. Since .htaccess files often contain authorization
# information, access is disallowed for security reasons. Comment
# these lines out if you want Web visitors to see the contents of
# .htaccess files. If you change the AccessFileName directive above,
# be sure to make the corresponding changes here.
#
# Also, folks tend to use names such as .htpasswd for password
# files, so this will protect those as well.
#
<Files ~ "^\.ht">
Order allow,deny
Deny from all
</Files>

#
# UseCanonicalName: (new for 1.3) With this setting turned on, whenever
# Apache needs to construct a self-referencing URL (a URL that refers back
# to the server the response is coming from) it will use ServerName and
# Port to form a "canonical" name. With this setting off, Apache will
# use the hostname:port that the client supplied, when possible. This
# also affects SERVER_NAME and SERVER_PORT in CGI scripts.
#
UseCanonicalName Off

#
# TypesConfig describes where the mime.types file (or equivalent) is
# to be found.
#
<IfModule mod_mime.c>
TypesConfig /etc/httpd/mime.types
</IfModule>

#
# DefaultType is the default MIME type the server will use for a document
# if it cannot otherwise determine one, such as from filename extensions.
# If your server contains mostly text or HTML documents, "text/plain" is
# a good value. If most of your content is binary, such as applications
# or images, you may want to use "application/octet-stream" instead to
# keep browsers from trying to display binary files as though they are
# text.
#
DefaultType text/plain

#
# The mod_mime_magic module allows the server to use various hints from the
# contents of the file itself to determine its type. The MIMEMagicFile
# directive tells the module where the hint definitions are located.
# mod_mime_magic is not part of the default server (you have to add
# it yourself with a LoadModule [see the DSO paragraph in the 'Global
# Environment' section], or recompile the server and include mod_mime_magic
# as part of the configuration), so it's enclosed in an <IfModule> container.
# This means that the MIMEMagicFile directive will only be processed if the
# module is part of the server.
#
<IfModule mod_mime_magic.c>
MIMEMagicFile /etc/httpd/magic
</IfModule>

#
# HostnameLookups: Log the names of clients or just their IP addresses
# e.g., www.apache.org (on) or 204.62.129.132 (off).
# The default is off because it'd be overall better for the net if people
# had to knowingly turn this feature on, since enabling it means that
# each client request will result in AT LEAST one lookup request to the
# nameserver.
#
HostnameLookups Off

#
# ErrorLog: The location of the error log file.
# If you do not specify an ErrorLog directive within a <VirtualHost>
# container, error messages relating to that virtual host will be
# logged here. If you *do* define an error logfile for a <VirtualHost>
# container, that host's errors will be logged there and not here.
#
ErrorLog /var/log/httpd/error_log

#
# LogLevel: Control the number of messages logged to the error_log.
# Possible values include: debug, info, notice, warn, error, crit,
# alert, emerg.
#
LogLevel warn

#
# The following directives define some format nicknames for use with
# a CustomLog directive (see below).
#
LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\"" combined
LogFormat "%h %l %u %t \"%r\" %>s %b" common
LogFormat "%{Referer}i -> %U" referer
LogFormat "%{User-agent}i" agent

#
# The location and format of the access logfile (Common Logfile Format).
# If you do not define any access logfiles within a <VirtualHost>
# container, they will be logged here. Contrariwise, if you *do*
# define per-<VirtualHost> access logfiles, transactions will be
# logged therein and *not* in this file.
#
CustomLog /var/log/httpd/access_log common


#
# Optionally add a line containing the server version and virtual host
# name to server-generated pages (error documents, FTP directory listings,
# mod_status and mod_info output etc., but not CGI generated documents).
# Set to "EMail" to also include a mailto: link to the ServerAdmin.
# Set to one of: On | Off | EMail
#
ServerSignature On


#
# Aliases: Add here as many aliases as you need (with no limit). The format is
# Alias fakename realname
#
<IfModule mod_alias.c>

#
# Note that if you include a trailing / on fakename then the server will
# require it to be present in the URL. So "/icons" isn't aliased in this
# example, only "/icons/". If the fakename is slash-terminated, then the
# realname must also be slash terminated, and if the fakename omits the
# trailing slash, the realname must also omit it.
#
Alias /interweb "/home/jasonk/www/html"

<Directory "/home/jasonk/www/html">
Options Indexes MultiViews
AllowOverride None
Order allow,deny
Allow from all
</Directory>

#
# ScriptAlias: This controls which directories contain server scripts.
# ScriptAliases are essentially the same as Aliases, except that
# documents in the realname directory are treated as applications and
# run by the server when requested rather than as documents sent to the client.
# The same rules about trailing "/" apply to ScriptAlias directives as to
# Alias.
#
#ScriptAlias /cgi-bin/ "/usr/local/apache/cgi-bin/"

#
# "/usr/local/apache/cgi-bin" should be changed to whatever your ScriptAliased
# CGI directory exists, if you have that configured.
#
#<Directory "/usr/local/apache/cgi-bin">
# AllowOverride None
# Options None
# Order allow,deny
# Allow from all
#</Directory>

</IfModule>
# End of aliases.



#
# Customize behaviour based on the browser
#
<IfModule mod_setenvif.c>

#
# The following directives modify normal HTTP response behavior.
# The first directive disables keepalive for Netscape 2.x and browsers that
# spoof it. There are known problems with these browser implementations.
# The second directive is for Microsoft Internet Explorer 4.0b2
# which has a broken HTTP/1.1 implementation and does not properly
# support keepalive when it is used on 301 or 302 (redirect) responses.
#
BrowserMatch "Mozilla/2" nokeepalive
BrowserMatch "MSIE 4\.0b2;" nokeepalive downgrade-1.0 force-response-1.0

#
# The following directive disables HTTP/1.1 responses to browsers which
# are in violation of the HTTP/1.0 spec by not being able to grok a
# basic 1.1 response.
#
BrowserMatch "RealPlayer 4\.0" force-response-1.0
BrowserMatch "Java/1\.0" force-response-1.0
BrowserMatch "JDK/1\.0" force-response-1.0

</IfModule>
# End of browser customization directives



#
# Caucho Servlet Engine Configuration
#
# Uncomment the following two lines to enable CSE

LoadModule caucho_module /usr/local/apache/libexec/mod_caucho.so
AddModule mod_caucho.c
CauchoHost localhost 6802
AddHandler caucho-request jsp
AddHandler caucho-request xtp
<IfModule mod_caucho.c>
CauchoConfigFile /etc/resin/resin.conf
<Location /resin-info>
SetHandler caucho-status
</Location>
</IfModule>

quinte17
29.10.02, 10:09
versuch einfach mal testweise, die files und den ordner auf chmod 777 zu stellen, obs dann läuft...
dann kommen wir der ursache ein wenig näher...
cu

netzmeister
29.10.02, 10:13
Hallo,

das hat doch mit dem Apachen nichts zu tun!

Ein 777 ... :confused: :rolleyes: das ist die Holzhammermethode.

Einfach mal Doku lesen. Und dann auf das Verzeichnis ein chmod a+rx machen.

r=lesen
x=durchsuchen

Viele Grüße

Eicke

smiler
29.10.02, 10:17
Schon probiert, und jetzt gleich nochmal.

Leider keine Aenderung .-((

Trotzdem danke

Smiler

smiler
29.10.02, 10:22
Selbst die "Nichtholzhammermethode" ;-), sprich nur ein a+x und a+r hilft nicht.
Da muss irgendwo in der Config ein generelles "no" fuer solche Sachen stehen. Bloss wo?

Kann man irgendwo generell Aliassa und aehnliches ausschalten im Apache? Wo geht das? Ich habe leider nichts gefunden. Und meine globalen Restriktions sind doch nicht sooo restriktiv, oder?

Danke

Smiler

netzmeister
29.10.02, 10:39
Hallo smiler,

Dein Eintrag ist falsch. Überprüfe da nochmal die Syntax.
Nimm den aus dem IF Module raus. So ein Kuddelmuddel. Das ist die Haupkonfiguration des
Servers!

Packe den Alias in ein eigenen Directory Eintrag, ganz am Ende der Serverkonfiguration.
Und dann bitte mit /bla_dir / Slash am Ende nicht vergessen.

Oder besser machst Du Deine Änderungen in eine seperate Datei. Die rufst Du
dann am Schluss mit einer include -Anweisung auf.

Diese Hobby-Admins :rolleyes:

Viele Grüße

Eicke

smiler
29.10.02, 11:14
Hallo Netzmeister,
danke fuer den tip
und danke fuer den hobbyadmin :rolleyes:

Und Du kannst mir glauben, dass ich mir die Doku durchgelesen habe. Ein "dezenter" tip, wo ich denn nun falschliege wuerde mir schon sehr weiterhelfen. Ich weiss einfach nicht, wo der Fehler liegen koennte.

Ein einzelner Alleinstehender "alias"-Eintrag klappt uebrigens auch nicht.

Und was? Den Aliaseintrag _in_ einen eigenen Directory-Eintrag? Laut Apache Doku gehoert "Alias" aber in die Serverconfig bzw. in einen virtualHost-Eintrag. Und da ich keinen virtual Host habe...

Und der Slash am Ende sollte eigentlich keine Bedeutung habe. jedenfalls habe ich es so verstanden (laut Doku), das _mit_ "/" ein eventueller Aufruf www.blah.de/test _nicht_ "gealiast" wird ein Aufruf der Form www.blah.de/test/ faellt dann unter die Aliaskonfiguration.
(Es klappt uebrigens mit oder ohne Slash am Ende derzeit nicht)
Und zu Hause, wo ich "hobbyadmin" bin hatte Slash onder nicht slash auch keine Auswirkung. Es klappte halt. Es sah ansonsten auch ziemlich aehnlich aus wie die gepostete Config, sonst haette ich das ganze <IF...>-Gerassel und so weiter nicht dringelassen.

Gruesse

Smiler

smiler
29.10.02, 11:49
O.K. ich hab's.

ein chmod a+x auf /home/userdir war die loesung.

vorher war es rwx------ und jetzt ist es rwx--x--x
(Sowas bloedes, da haette ich auch eher drauf kommen koennen)

und es klappt.

(Und der Alias steht ganz allein und "verloren" in der Serverkonfig.
EIgentlich sollte ich glatt nochmal probieren, ob es auch funktioniert, wenn ich den Alias in das <If...>-Gerassel schreibe. ;) )

Gibt es gegen diese Einstellung irgendwelche Sicherheitsbedenken?

Smiler

(Die Loesung fiel mir uebrigens ein, als ich mich ins Auto gesetzt hatte, um nach Hause zu fahren, um die Suse-httpd-config-files zu holen und mal Zeile fuer Zeile zu vergleichen.)

netzmeister
29.10.02, 12:15
Hallo smiler,

na also. Das mit den Rechten hatte ich ja oben schon geschrieben.

Am besten erstellst Du Dir eine eigene Konfigurationsdatei!

Diese rufst Du am Schluss der httpd.conf mittels Include /etc/httpd/deine_eigene.conf auf. Da kannst Du dann anch Herzenslust drin rumschmieren :p

Ist ja nur so ein Gedanke.

Viele Grüße

Eicke

smiler
29.10.02, 13:36
Hi netzmeister,
ja, ich war mir eigentlich auch fast sicher, dass es irgendwie an der Rechteverteilung liegen muss, kam aber einfach nicht auf die (eigentlich naheliegende) Idee, mal eine Verzeichnisebene hoeher zu schauen (Obwohl ich ein aehnliches Problem frueher auch schon mal hatte). Ich habe da einfach nicht dran gedacht.
Ich werde den Alias wahrscheinlich auch wirklich auslagern, weil die httpd.conf schon so ziemlich lang ist, und man muss sie ja nicht unnoetig groesser machen.

Aber den "Hobby-Admin"....., grrrr ;)

Gruesse

Smiler

MichlS
31.10.02, 21:42
habe das gleiche "problem" ..
funzt auch mit wrx--x--x nicht ... ohne "/" am schluss keine musik :cool:
evtl. gibts ja noch ne andere lösung

bin auch "hobby admin" und bin stolz drauf ;) :D

dafür ist ja ein forum da .. "user helfen user" gelle

greez mike

smiler
01.11.02, 09:47
Hi,
wie hast du den Alias geschrieben?

wenn Du schreibst:

Alias /testverzeichnis /home/testuser/html
(Das ist was anderes als "Alias /testverzeichnis/ /home/testuser/html/"!)

Es sollte es eigentlich gehen, wenn Du in der Definition die Verzeichnisse ohn abschliessendes Slash schreibst. Wenn Du aber in de Alias-Definition auch den Slash an das Ende machst, dann musst Du den Slash auch bei der Adressangabe mit angeben. Dann ist im Alias die "slash-lose" angabe naemlich nicht mit einbezogen.
Hoffe, diese konfuse Antwort hilft ein bisschen.

Smiler

MichlS
01.11.02, 21:19
UseCanonicalName Off

das in der httpd.conf eintragen und die geschichte ist erledigt ;)

greez mike