Thanks Michael, Michael Hasenstein wrote:

At least on SuSE Linux 6.3, maybe it was there in 6.2 also, don't remember, the default Apache homepage uses SSI. Look at /usr/local/httpd/htdocs/index.html and at the apache configuration to see how it works. If you have an older version of SuSE Linux, simply get the

My 6.1 version doesn't use SSI.

6.3 apache.rpm from ftp.suse.com or any mirror.

I presume glibc differences won't have any effect then? I suppose I should trust you, since you work at SuSE, but I just thought I'd check, considering the time you wrote it ;-) Thanks for your help, Chris PS. In case anyone *is* still scratching their heads over this (wishfull thinking...) and this does make a difference: that directory I gave is aliased to http://serverroot/primary/webs, and I have the mod_include.so and mod_include.c loaded (there were loaded even before I tried to set this up). -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Because I am relative new in Linux world i don't understand few things. I know there are many Linux distributions. I don't understand why if we talk about "serious" Linux distro, conversation always ends with Red Hat or sometimes Debian. I keep hearing all the time words like "SuSE nice desktop system", SuSE cool "Win OS", "Windows like" Linux" etc ... I used SuSE 6.0,Red Hat 6.0. Now I am running SuSE 6.3 . I was searching distribution which is the best for me. Now I know it's SuSE . I hate cynic comments "a VERY user friendly distro" from Deb and Slack "power users" >:D . Isn't the point of Linux community to have user friendly OS and to show Linux to the people and not to stay OS for hackers, sys and net admins. And that is not going to happen if old gurus (with all respect from my side) keep making jokes with new users and new distribution. My question is: Do Red Hat or Debian have more pluses when we talk about stability and speed of server machines then SuSE? I don't like the way that Red Hat goes...it is exactly the same like MS few years ago... I found my favorite distribution and I am not going to change to another :) Thank you all for this valuable source of information ... Greetings, PaTLo ***First Linux on my machine was installed by WOMAN *** -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Anel Hidic wrote: [snip]

My question is: Do Red Hat or Debian have more pluses when we talk about stability and speed of server machines then SuSE?

There is more to the equation than speed and stability. Security is also very important. In my security list, I receive many SuSE updates to packages long before Red Hat sends out the security advisories. Red Hat has a very negative reputation concerning security. I cannot comment on speed as I don't have SuSE and Red Hat installed on comparable hardware. I can comment that Linux NFS really DOES blow chunks compared to Solaris. I have run speed tests in that regard, and Linux is much slower, but Solaris on (an unsupported) Intel is about as stable as Windows 95.

I don't like the way that Red Hat goes...it is exactly the same like MS few years ago...

I found my favorite distribution and I am not going to change to another :)

I thought that way for a while. But using one distro is like eating with one utensil. Even the Japanese and Chinese do not limit themselves to just chopsticks. Likewise, I found both SuSE and Red Hat are better suited to different tasks.

Thank you all for this valuable source of information ...

Greetings,

PaTLo

***First Linux on my machine was installed by WOMAN ***

Cool!!! -- George Toft http://www.georgetoft.com -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Thanks everyone for your help so far, it is appreciated. I'm also attaching my /etc/httpd/httpd.conf file, I hope this doesn't inconvenience anyone too much. This is just a last ditch attempt with this very helpful group before I go off to find an apache mailing list. Hope you can help before I have to resort to that though :( clarge@gizmo.macn.bc.ca wrote:

...

My 6.1 version doesn't use SSI.

Our machine that runs a default 6.1 install can run them files. We just uncomented out the server side lines and it worked. Mind we didn't make the pages. they came with an radius accounting package.

I've got those lines uncommented, but there must be something wrong with them. I did manage to get the server to parse the files with SSI commands in, sort of. I ScriptAlias'd the root directory (/webs/primary), and when I reloaded the page, it had been parsed, but it showed errors with the directive. This was probably because the directive was simply <!--#include virtual="footer.html" --> which, being in the same directory, was also parsed and produced the error because it wasn't parsable/runable, i.e. wasn't a script (remember, I ScriptAlias'd the directory). I can't leave the directory ScriptAlias'd because not all documents to be server are parsable, and I get these errors. I took the ScriptAlias off again and the docs weren't parsed. I even tried to put the following directive in for the directory: SetHandler server-parsed which should mean that every file in that directory is server parsed, which should have resulted in the same as I was getting about, i.e. parsable file being parsed, but returning errors on the non-parsable footer.html. It looks like the AddHandler/SetHandler isn't working at all. As I mentioned before, the necessary directories are marked with Options +ExecCGI +Includes and I also have AddHandler server-parsed .shtml and all my server parsable files *do* have .shtml extensions. I'm not even sure if the cgi-script handler is working properly. It *appears* to be working for the root-directory (i.e. /) but doesn't work in the /webs/primary/cgi-bin/ directory. I'm really at a loss here. There's hair scattered everywhere.... Maybe I should find an apache mailing list. Thanks for any further help any of you can give, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ ## ## 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/httpd.conf/srm.conf and then /usr/local/httpd/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. # # Do NOT add a slash at the end of the directory path. # ServerRoot "/usr/local/httpd" # # 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/lock/subsys/httpd/httpd.accept.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/log/httpd.apache_runtime_status # # In the standard configuration, the server will process this file, # 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. # MaxRequestsPerChild 30 # # 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 is which modules are loaded is important. Don't change # the order below without expert advice. # # Example: # LoadModule foo_module libexec/mod_foo.so LoadModule mmap_static_module /usr/lib/apache/mod_mmap_static.so LoadModule env_module /usr/lib/apache/mod_env.so LoadModule config_log_module /usr/lib/apache/mod_log_config.so LoadModule agent_log_module /usr/lib/apache/mod_log_agent.so LoadModule referer_log_module /usr/lib/apache/mod_log_referer.so LoadModule mime_magic_module /usr/lib/apache/mod_mime_magic.so LoadModule mime_module /usr/lib/apache/mod_mime.so LoadModule negotiation_module /usr/lib/apache/mod_negotiation.so LoadModule status_module /usr/lib/apache/mod_status.so LoadModule info_module /usr/lib/apache/mod_info.so LoadModule includes_module /usr/lib/apache/mod_include.so LoadModule autoindex_module /usr/lib/apache/mod_autoindex.so LoadModule dir_module /usr/lib/apache/mod_dir.so LoadModule cgi_module /usr/lib/apache/mod_cgi.so LoadModule asis_module /usr/lib/apache/mod_asis.so LoadModule imap_module /usr/lib/apache/mod_imap.so LoadModule action_module /usr/lib/apache/mod_actions.so LoadModule speling_module /usr/lib/apache/mod_speling.so LoadModule userdir_module /usr/lib/apache/mod_userdir.so LoadModule proxy_module /usr/lib/apache/libproxy.so LoadModule alias_module /usr/lib/apache/mod_alias.so LoadModule rewrite_module /usr/lib/apache/mod_rewrite.so LoadModule access_module /usr/lib/apache/mod_access.so LoadModule auth_module /usr/lib/apache/mod_auth.so LoadModule anon_auth_module /usr/lib/apache/mod_auth_anon.so LoadModule dbm_auth_module /usr/lib/apache/mod_auth_dbm.so LoadModule db_auth_module /usr/lib/apache/mod_auth_db.so LoadModule digest_module /usr/lib/apache/mod_digest.so LoadModule cern_meta_module /usr/lib/apache/mod_cern_meta.so LoadModule expires_module /usr/lib/apache/mod_expires.so LoadModule headers_module /usr/lib/apache/mod_headers.so LoadModule usertrack_module /usr/lib/apache/mod_usertrack.so LoadModule example_module /usr/lib/apache/mod_example.so LoadModule unique_id_module /usr/lib/apache/mod_unique_id.so LoadModule setenvif_module /usr/lib/apache/mod_setenvif.so LoadModule perl_module /usr/lib/apache/libperl.so LoadModule php3_module /usr/lib/apache/libphp3.so # 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_mmap_static.c AddModule mod_env.c AddModule mod_log_config.c AddModule mod_log_agent.c AddModule mod_log_referer.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_proxy.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_auth_db.c AddModule mod_digest.c AddModule mod_cern_meta.c AddModule mod_expires.c AddModule mod_headers.c AddModule mod_usertrack.c AddModule mod_example.c AddModule mod_unique_id.c AddModule mod_so.c AddModule mod_setenvif.c AddModule mod_perl.c AddModule mod_php3.c # # 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 # # 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 nogroup on these systems! # User wwwrun Group nogroup # # 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 root@localhost # # 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. # #ServerName allen.suse.de # # 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 "/usr/local/httpd/htdocs" # # 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 /> # disallowed Indexes 27/01/00 Options -Indexes FollowSymLinks AllowOverride None </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. # # # 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. # removed Indexes option 27/01/00 # Options FollowSymLinks # # 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 None # # Controls who can get stuff from this server. # Order allow,deny Allow from all </Directory> # # UserDir: The name of the directory which is appended onto a user's home # directory if a ~user request is received. # UserDir public_html # # Control access to UserDir directories. The following is an example # for a site where these directories are restricted to read-only. # # # AllowOverride FileInfo AuthConfig Limit # Options MultiViews Indexes SymLinksIfOwnerMatch IncludesNoExec # <Limit GET POST OPTIONS PROPFIND> # Order allow,deny # Allow from all # </Limit> # <Limit PUT DELETE PATCH PROPPATCH MKCOL COPY MOVE LOCK UNLOCK> # Order deny,allow # Deny from all # </Limit> #</Directory> # # DirectoryIndex: Name of the file or files to use as a pre-written HTML # directory index. Separate multiple entries with spaces. # added index.shtml before index.html 27/01/00 # DirectoryIndex index.shtml index.html # # 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. # Order allow,deny Deny from all </Files> # # CacheNegotiatedDocs: By default, Apache sends "Pragma: no-cache" with each # document that was negotiated on the basis of content. This asks proxy # servers not to cache the document. Uncommenting the following line disables # this behavior, and proxies will be allowed to cache the documents. # #CacheNegotiatedDocs # # 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 On # # TypesConfig describes where the mime.types file (or equivalent) is # to be found. # TypesConfig /etc/httpd/mime.types # # 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 # # If you would like to have agent and referer logfiles, uncomment the # following directives. # #CustomLog /var/log/httpd.referer_log referer #CustomLog /var/log/httpd.agent_log agent # # If you prefer a single logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # #CustomLog /var/log/httpd.access_log combined # # 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 # # 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/".. #8 Alias /icons/ "/usr/local/httpd/icons/" # removed option Indexes 27/01/00 Options MultiViews AllowOverride None Order allow,deny Allow from all </Directory> Alias /hilfe/ /usr/doc/susehilf/ Alias /doc/ /usr/doc/ Alias /cgi-bin-sdb/ /usr/local/httpd/cgi-bin/ Alias /sdb/ /usr/doc/sdb/ # # 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/httpd/cgi-bin/" # added ScriptAlias for primary and test cgi-bin directories 27/01/00 ScriptAlias /webs/primary/cgi-bin "/usr/local/httpd/htdocs/wwwroot/primary/cgi-bin" ScriptAlias /webs/test/cgi-bin "/usr/local/httpd/htdocs/wwwroot/test/cgi-bin" # added in ScriptAlias for primary and test root directories 27/01/00 #ScriptAlias /webs/primary "/usr/local/httpd/htdocs/wwwroot/primary" #ScriptAlias /webs/test "/usr/local/httpd/htdocs/wwwroot/test" # # "/usr/local/httpd/cgi-bin" should be changed to whatever your ScriptAliased # CGI directory exists, if you have that configured. # AllowOverride None Options None Order allow,deny Allow from all </Directory> # cgi-bin for SuSE help system # using SetHandler AllowOverride None Options +ExecCGI -Includes SetHandler cgi-script </Directory> # enable perl for cgi-bin # AddHandler perl-script .pl PerlHandler Apache::Registry PerlSendHeader On Options +ExecCGI </Location> # directory specs for primary and test webs added 27/01/00 AddHandler server-parsed .shtml Options +ExecCGI +Includes </Directory> Options +ExecCGI +Includes </Directory> Options +ExecCGI +Includes </Directory> Options +ExecCGI +Includes </Directory> # # Redirect allows you to tell clients about documents which used to exist in # your server's namespace, but do not anymore. This allows you to tell the # clients where to look for the relocated document. # Format: Redirect old-URI new-URL # # # Directives controlling the display of server-generated directory listings. # # # FancyIndexing is whether you want fancy directory indexing or standard # IndexOptions FancyIndexing # # AddIcon* directives tell the server which icon to show for different # files or filename extensions. These are only displayed for # FancyIndexed directories. # AddIconByEncoding (CMP,/icons/compressed.gif) x-compress x-gzip AddIconByType (TXT,/icons/text.gif) text/* AddIconByType (IMG,/icons/image2.gif) image/* AddIconByType (SND,/icons/sound2.gif) audio/* AddIconByType (VID,/icons/movie.gif) video/* AddIcon /icons/binary.gif .bin .exe AddIcon /icons/binhex.gif .hqx AddIcon /icons/tar.gif .tar AddIcon /icons/world2.gif .wrl .wrl.gz .vrml .vrm .iv AddIcon /icons/compressed.gif .Z .z .tgz .gz .zip AddIcon /icons/a.gif .ps .ai .eps AddIcon /icons/layout.gif .html .shtml .htm .pdf AddIcon /icons/text.gif .txt AddIcon /icons/c.gif .c AddIcon /icons/p.gif .pl .py AddIcon /icons/f.gif .for AddIcon /icons/dvi.gif .dvi AddIcon /icons/uuencoded.gif .uu AddIcon /icons/script.gif .conf .sh .shar .csh .ksh .tcl AddIcon /icons/tex.gif .tex AddIcon /icons/bomb.gif core AddIcon /icons/back.gif .. AddIcon /icons/hand.right.gif README AddIcon /icons/folder.gif ^^DIRECTORY^^ AddIcon /icons/blank.gif ^^BLANKICON^^ # # DefaultIcon is which icon to show for files which do not have an icon # explicitly set. # DefaultIcon /icons/unknown.gif # # AddDescription allows you to place a short description after a file in # server-generated indexes. These are only displayed for FancyIndexed # directories. # Format: AddDescription "description" filename # #AddDescription "GZIP compressed document" .gz #AddDescription "tar archive" .tar #AddDescription "GZIP compressed tar archive" .tgz # # ReadmeName is the name of the README file the server will look for by # default, and append to directory listings. # # HeaderName is the name of a file which should be prepended to # directory indexes. # # The server will first look for name.html and include it if found. # If name.html doesn't exist, the server will then look for name.txt # and include it as plaintext if found. # ReadmeName README HeaderName HEADER # # IndexIgnore is a set of filenames which directory indexing should ignore # and not include in the listing. Shell-style wildcarding is permitted. # IndexIgnore .??* *~ *# HEADER* README* RCS CVS *,v *,t # # AddEncoding allows you to have certain browsers (Mosaic/X 2.1+) uncompress # information on the fly. Note: Not all browsers support this. # Despite the name similarity, the following Add* directives have nothing # to do with the FancyIndexing customization directives above. # AddEncoding x-compress Z AddEncoding x-gzip gz # # AddLanguage allows you to specify the language of a document. You can # then use content negotiation to give a browser a file in a language # it can understand. Note that the suffix does not have to be the same # as the language keyword --- those with documents in Polish (whose # net-standard language code is pl) may wish to use "AddLanguage pl .po" # to avoid the ambiguity with the common suffix for perl scripts. # AddLanguage en .en AddLanguage fr .fr AddLanguage de .de AddLanguage da .da AddLanguage el .el AddLanguage it .it # # LanguagePriority allows you to give precedence to some languages # in case of a tie during content negotiation. # Just list the languages in decreasing order of preference. # LanguagePriority en fr de # # AddType allows you to tweak mime.types without actually editing it, or to # make certain files to be certain types. # # For example, the PHP3 module (not part of the Apache distribution - see # http://www.php.net) will typically use: # AddType application/x-httpd-php3 .php3 AddType application/x-httpd-php3-source .phps AddType application/x-httpd-php3 .phtml # # AddHandler allows you to map certain file extensions to "handlers", # actions unrelated to filetype. These can be either built into the server # or added with the Action command (see below) # # If you want to use server side includes, or CGI outside # ScriptAliased directories, uncomment the following lines. # # To use CGI scripts: # added .pl extension to AddHandler cgi-script 27/01/00 # AddHandler cgi-script .cgi .pl # # To use server-parsed HTML files # uncommented 27/01/00 # AddType text/html .shtml AddHandler server-parsed .shtml # # Uncomment the following line to enable Apache's send-asis HTTP file # feature # #AddHandler send-as-is asis # # If you wish to use server-parsed imagemap files, use # #AddHandler imap-file map # # To enable type maps, you might want to use # #AddHandler type-map var # # Action lets you define media types that will execute a script whenever # a matching file is called. This eliminates the need for repeated URL # pathnames for oft-used CGI file processors. # Format: Action media/type /cgi-script/location # Format: Action handler-name /cgi-script/location # # # MetaDir: specifies the name of the directory in which Apache can find # meta information files. These files contain additional HTTP headers # to include when sending the document # #MetaDir .web # # MetaSuffix: specifies the file name suffix for the file containing the # meta information. # #MetaSuffix .meta # # Customizable error response (Apache style) # these come in three flavors # # 1) plain text #ErrorDocument 500 "The server made a boo boo. # n.b. the (") marks it as text, it does not get output # # 2) local redirects #ErrorDocument 404 /missing.html # to redirect to local URL /missing.html #ErrorDocument 404 /cgi-bin/missing_handler.pl # N.B.: You can redirect to a script or a document using server-side-includes. # # 3) external redirects #ErrorDocument 402 http://some.other_server.com/subscription_info.html # N.B.: Many of the environment variables associated with the original # request will *not* be available to such a script. # # 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 # # Allow server status reports, with the URL of http://servername/server-status # Change the ".your_domain.com" to match your domain to enable. # SetHandler server-status Order deny,allow Deny from all Allow from localhost </Location> # # Allow remote server configuration reports, with the URL of # http://servername/server-info (requires that mod_info.c be loaded). # Change the ".your_domain.com" to match your domain to enable. # # # SetHandler server-info # Order deny,allow # Deny from all # Allow from .your_domain.com #</Location> # # There have been reports of people trying to abuse an old bug from pre-1.1 # days. This bug involved a CGI script distributed as a part of Apache. # By uncommenting these lines you can redirect these attacks to a logging # script on phf.apache.org. Or, you can record them yourself, using the script # support/phf_abuse_log.cgi. # # # Deny from all # ErrorDocument 403 http://phf.apache.org/phf_abuse_log.cgi #</Location> # # Proxy Server directives. Uncomment the following lines to # enable the proxy server: # #<IfModule mod_proxy.c> #ProxyRequests On # # # Order deny,allow # Deny from all # Allow from .your_domain.com #</Directory> # # Enable/disable the handling of HTTP/1.1 "Via:" headers. # ("Full" adds the server version; "Block" removes all outgoing Via: headers) # Set to one of: Off | On | Full | Block # #ProxyVia On # # To enable the cache as well, edit and uncomment the following lines: # (no cacheing without CacheRoot) # #CacheRoot "/var/cache/httpd" #CacheSize 5 #CacheGcInterval 4 #CacheMaxExpire 24 #CacheLastModifiedFactor 0.1 #CacheDefaultExpire 1 #NoCache a_domain.com another_domain.edu joes.garage_sale.com #</IfModule> # End of proxy directives. ### Section 3: Virtual Hosts # # VirtualHost: If you want to maintain multiple domains/hostnames on your # machine you can setup VirtualHost containers for them. # Please see the documentation at URL:http://www.apache.org/docs/vhosts/ # for further details before you try to setup virtual hosts. # You may use the command line option '-S' to verify your virtual host # configuration. # # If you want to use name-based virtual hosts you need to define at # least one IP address (and port number) for them. # #NameVirtualHost 12.34.56.78:80 #NameVirtualHost 12.34.56.78 # # VirtualHost example: # Almost any Apache directive may go into a VirtualHost container. # #<VirtualHost ip.address.of.host.some_domain.com> # ServerAdmin webmaster@host.some_domain.com # DocumentRoot /www/docs/host.some_domain.com # ServerName host.some_domain.com # ErrorLog logs/host.some_domain.com-error_log # CustomLog logs/host.some_domain.com-access_log common #</VirtualHost> # #</VirtualHost> -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Chris Reeves wrote:

Hello again everyone!!

I've finally managed to sort out the problem with the SSI.

Chris Reeves wrote:

...

Sorry to have troubled you all, I'll ask on an apache list,

I was in the middle of writing a message for the comp.infosystems.www.servers.unix newsgroup, when I started to edit the following to make it look cleaner.

--- Options +ExecCGI +Includes </Directory> ---

I was changing the 'wwwroot' directory name to 'webs', because on the server 'webs' is simply a symlink to 'wwwroot' (a relic of the move from NT with IIS). It then occured to me: I was enabling includes for the wwwroot directory and accessing it through the webs symlink - does this make a difference, I asked... A quick change of URL in netscape and bingo. Pages appeared with SSI actually working!! It does make a difference.

I said to myself (and actually wrote in my online computing diary) earlier today that this would be something obvious. Well it was - a simple symlink. The wwwroot directory is no more, and has been renamed to webs, and all problems are solved, including the scripting problems that I was having.

You have *no* idea how relieved I am. I have been working at this virtually non-stop for the past eight or nine hours...

Thank you to *everyone* who tried to assist in solving this problem, your help (and moral support - at least I felt that *someone* out there cared ;-) was very much appreciated. Unfortunately I didn't give you enough information to figure this one out :(

And I do apologise for putting people through this (and also special apologies for those on slow dialup connections who had to download my huge httpd.conf file - I can sympathise). And yet another apology for this long 'problem solved' message...

I've certainly learnt a lot today (but haven't actually *done* anything per se - I did *literally* spend the last eight hours editing httpd.conf and restarting apache :-( ). Basically a wasted day :-(

Moral of the story: watch your symlinks. I won't forget that in a hurrry!

I'm just glad it's working. Thanks again, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\

Thank you for posting your solution! You have added to the Linux community's store of knowledge! JLK -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/

Michael Hasenstein wrote:

Don't remember... but even if not, it doesn't matter, the important things are a) the httpd.conf and b) the example index.html with SSI, not the binary.

There is little or no difference between the SSI implementations in my httpd.conf compared to the 6.3 version. Sorry to have troubled you all, I'll ask on an apache list, Chris -- __ _ -o)/ / (_)__ __ ____ __ Chris Reeves /\\ /__/ / _ \/ // /\ \/ / ICQ# 22219005 _\_v __/_/_//_/\_,_/ /_/\_\ -- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/