Robert Bartlett Baron, reported over 1 year ago Using xdmod-setup, I created an admin account:

======================================================================== Create Admin User

Username: admin Password: (confirm) Password: First name: rob Last name: baron Email address: robbaron@bu.edu

Admin user created.

Press ENTER to continue.

It appears in users:

select * from moddb.Users; +----+-------------+--------------------------------------------------------------+----------------------+------------+-------------+-----------+---------------------+---------------------+-----------------------+-------------------+-----------+-----------------+------------------+----------------------------------+---------------------+-----------+--------+ | id | username | password | email_address | first_name | middle_name | last_name | time_created | time_last_updated | password_last_updated | account_is_active | person_id | organization_id | field_of_science | token | token_expiration | user_type | sticky | +----+-------------+--------------------------------------------------------------+----------------------+------------+-------------+-----------+---------------------+---------------------+-----------------------+-------------------+-----------+-----------------+------------------+----------------------------------+---------------------+-----------+--------+ | 1 | Public User | NULL | public@ccr.xdmod.org | Public | | User | 2022-03-31 20:01:24 | 2022-03-31 20:01:24 | 0000-00-00 00:00:00 | 1 | -1 | -1 | 0 | NULL | 0000-00-00 00:00:00 | 2 | 0 | | 6 | admin | $2y$10$ov69QG3GAtHKWIIVTq7i/OQq/jzwAEkbginypTpOMtuXP0HpL5G8O | robbaron@bu.edu | rob | | baron | 2022-04-04 15:05:26 | 2022-04-04 15:05:26 | 0000-00-00 00:00:00 | 1 | -1 | 0 | 0 | 35nBViHZvZexN1AZ3M70yKIVYWUNPNjx | 2022-05-04 15:05:26 | 2 | 0 | +----+-------------+--------------------------------------------------------------+----------------------+------------+-------------+-----------+---------------------+---------------------+-----------------------+-------------------+-----------+-----------------+------------------+----------------------------------+---------------------+-----------+--------+ 2 rows in set (0.01 sec)

And Here:

MariaDB [moddb]> select * from user_acls; +-------------+---------+--------+ | user_acl_id | user_id | acl_id | +-------------+---------+--------+ | 1 | 1 | 1 | | 3 | 6 | 2 | | 2 | 6 | 6 | +-------------+---------+--------+ 3 rows in set (0.00 sec)

Any suggestions as what I am missing? Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Everything you've shown in the database looks fine. What happens when to try to sign in? If you're familiar with the developer tools in your web browser, please check the response from the server when you attempt to sign in and send that to us. If you need instructions to do that let me know what browser you're using.

Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr Robert Bartlett Baron , said over 1 year ago I'm assuming you mean the javascript console. here are all of the messages:

[Log] main_tab_panel#tg_summary (xdmod.apps.nerc-shift-0.rc.fas.harvard.edu, line 23) [Error] Failed to load resource: the server responded with a status of 404 (Not Found) (quick_filters, line 0) [Error] TypeError: undefined is not an object (evaluating 'root.length') readRecords (ext-all-debug-w-comments.js:40767) loadData (ext-all-debug-w-comments.js:37810) callback (QuickFilterStore.js:78) handleFailure (ext-all-debug-w-comments.js:6557) f (ext-base.js:1:18146) m (ext-base.js:1:18304) (anonymous function) (ext-base.js:1:8610)

/ here is where the attempt to log in occurred /

[Error] Failed to load resource: the server responded with a status of 404 (Not Found) (login, line 0) [Error] TypeError: null is not an object (evaluating 'data.message') callback (CCR.js:1235) handleFailure (ext-all-debug-w-comments.js:6557) f (ext-base.js:1:18146) m (ext-base.js:1:18304) (anonymous function) (ext-base.js:1:8610)

Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Is there a "network" tab or something similar in your console? This will contain each response from the server. Whatever is in the response must not be valid, but seeing what it is would help me. Likewise, knowing which request is generating the 404 would help.

Jeff

Robert Bartlett Baron , said over 1 year ago Both logins have the same message, even though the user-interface.php and other php scripts do return valid responses.

Robert Bartlett Baron , said over 1 year ago image

Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Do you have mod_rewrite enabled? The "/rest/..." URL should be rewritten by Apache and I'm guessing that isn't happening resulting in the 404. Is there anything else in your Apache configuration that could be interfering with this?

Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr Robert Bartlett Baron , said over 1 year ago How would you like me to confirm that mod_rewrite is enabled?

Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Run this command on your web server:

httpd -M | grep rewrite

If there is no output then it isn't enabled. You should see something like "rewrite_module (shared)".

You can also check /etc/httpd/conf.modules.d/rewrite.load to see if the module is being loaded there.

If it appears that it is loaded you can look at your apache error_log (check the configuration of the virtual host for which file).

Jeff

sh-4.2$ grep -R "LoadModule" * | grep "rewrite" conf.modules.d/00-base.conf:LoadModule rewrite_module modules/mod_rewrite.so

sh-4.2$ grep -R "conf.modules.d" conf/httpd.conf:Include conf.modules.d/.conf

Is this what you are asking for?

Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert, What was the output from "httpd -M | grep rewrite"?

Jeff

$ httpd -M | grep rewrite
rewrite_module (shared)

Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert, Thank you, I just wanted to be sure about that. Is there anything else in your apache configuration that might affect this? Did you make any modifications to the provided template?

Do you see this in the virtual host:

<Directory /usr/share/xdmod/html/rest>
    RewriteEngine On
    RewriteRule (.*) index.php [L]
</Directory>

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Please let us know if this is still an issue for you.

Thanks, Jeff

I have made modifications to the apache config file. Kubernetes/OpenShift will handle the SSH part of the connection at either the ingress or the route. I will add the section that you suggested (it was not present) and see if I can log in then. I'll probably know either tonight or tomorrow.

Rob. Robert Bartlett Baron , said over 1 year ago After adding the "Directory /usr/share/xdmod/html/rest" section to the configuration, I seem to be able to log in, though I question if I am fully logged as there is no indication in the interface that have done so (see the attached xdmod.jpg image).

On the plus side, there are no errors that I can find and one time I logged in, I saw my account name fly by.

And here is the httpd.conf file:

This is the main Apache HTTP server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.

In particular, see

<URL:http://httpd.apache.org/docs/2.4/mod/directives.html>

for a discussion of each configuration directive.

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.

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 'log/access_log'

with ServerRoot set to '/www' will be interpreted by the

server as '/www/log/access_log', where as '/log/access_log' will be

interpreted as '/log/access_log'.

ServerRoot: The top of the directory tree under which the server's

configuration, error, and log files are kept.

Do not add a slash at the end of the directory path. If you point

ServerRoot at a non-local disk, be sure to specify a local disk on the

Mutex directive, if file-based mutexes are used. If you wish to share the

same ServerRoot for multiple httpd daemons, you will need to change at

least PidFile.

# ServerRoot "/etc/httpd"

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, instead of the default. See also the

directive.

Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses.

Listen 12.34.56.78:80

Listen 8080

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.

Statically compiled modules (those listed by `httpd -l') do not need

to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so

# Include conf.modules.d/*.conf

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.

It is usually good practice to create a dedicated user and group for

running httpd, as with most system services.

# User apache Group apache

'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

definition. These values also provide defaults for

any containers you may define later in the file.

All of these directives may appear inside containers,

in which case these default settings will be overridden for the

virtual host being defined.

ServerAdmin: Your address, where problems with the server should be

e-mailed. This address appears on some server-generated pages, such

as error documents. e.g. admin@your-domain.com

# ServerAdmin root@localhost

ServerName gives the name and port that the server uses to identify itself.

This can often be determined automatically, but we recommend you specify

it explicitly to prevent problems during startup.

If your host doesn't have a registered DNS name, enter its IP address here.

# ServerName xdmod.apps.nerc-shift-0.rc.fas.harvard.edu:8080

Deny access to the entirety of your server's filesystem. You must

explicitly permit access to web content directories in other

blocks below.

    Options FollowSymLinks
    AllowOverride All
    DirectoryIndex index.php
    Require all granted

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.

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/share/xdmod/html"

Relax access to content within /var/www.

# <Directory "/var/www"> AllowOverride None

Allow open access:

Require all granted

<Directory /usr/share/xdmod/html/rest> RewriteEngine On RewriteRule (.*) index.php [L]

Further relax access to the default document root:

<Directory "/var/www/html"> #

Possible values for the Options directive are "None", "All",

# or any combination of:
#   Indexes Includes FollowSymLinks SymLinksifOwnerMatch ExecCGI MultiViews
#
# Note that "MultiViews" must be named *explicitly* --- "Options All"
# doesn't give it to you.
#
# The Options directive is both complicated and important.  Please see
# http://httpd.apache.org/docs/2.4/mod/core.html#options
# for more information.
#
Options Indexes FollowSymLinks

#
# AllowOverride controls what directives may be placed in .htaccess files.
# It can be "All", "None", or any combination of the keywords:
#   Options FileInfo AuthConfig Limit
#
AllowOverride None

#
# Controls who can get stuff from this server.
#
Require all granted

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

DirectoryIndex index.html

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

# <Files ".ht*"> Require all denied

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a

container, error messages relating to that virtual host will be

logged here. If you do define an error logfile for a

container, that host's errors will be logged there and not here.

# ErrorLog "logs/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 # You need to enable mod_logio.c to use %I and %O LogFormat "%h %l %u %t \"%r\" %>s %b \"%{Referer}i\" \"%{User-Agent}i\" %I %O" combinedio # # The location and format of the access logfile (Common Logfile Format). # If you do not define any access logfiles within a # container, they will be logged here. Contrariwise, if you *do* # define per- access logfiles, transactions will be # logged therein and *not* in this file. # #CustomLog "logs/access_log" common # # If you prefer a logfile with access, agent, and referer information # (Combined Logfile Format) you can use the following directive. # CustomLog "logs/access_log" combined # # Redirect: Allows you to tell clients about documents that used to # exist in your server's namespace, but do not anymore. The client # will make a new request for the document at its new location. # Example: # Redirect permanent /foo http://www.example.com/bar # # Alias: Maps web paths into filesystem paths and is used to # access content that does not live under the DocumentRoot. # Example: # Alias /webpath /full/filesystem/path # # If you include a trailing / on /webpath then the server will # require it to be present in the URL. You will also likely # need to provide a section to allow access to # the filesystem path. # # ScriptAlias: This controls which directories contain server scripts. # ScriptAliases are essentially the same as Aliases, except that # documents in the target 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/ "/var/www/cgi-bin/"

"/var/www/cgi-bin" should be changed to whatever your ScriptAliased

CGI directory exists, if you have that configured.

# <Directory "/var/www/cgi-bin"> AllowOverride None Options None Require all granted

# # TypesConfig points to the file containing the list of mappings from # filename extension to MIME-type. # TypesConfig /etc/mime.types # # AddType allows you to add to or override the MIME configuration # file specified in TypesConfig for specific file types. # #AddType application/x-gzip .tgz # # AddEncoding allows you to have certain browsers uncompress # information on the fly. Note: Not all browsers support this. # #AddEncoding x-compress .Z #AddEncoding x-gzip .gz .tgz # # If the AddEncoding directives above are commented-out, then you # probably should define those extensions to indicate media types: # AddType application/x-compress .Z AddType application/x-gzip .gz .tgz # # 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 directive (see below) # # To use CGI scripts outside of ScriptAliased directories: # (You will also need to add "ExecCGI" to the "Options" directive.) # #AddHandler cgi-script .cgi # For type maps (negotiated resources): #AddHandler type-map var # # Filters allow you to process content before it is sent to the client. # # To parse .shtml files for server-side includes (SSI): # (You will also need to add "Includes" to the "Options" directive.) # AddType text/html .shtml AddOutputFilter INCLUDES .shtml

Specify a default charset for all content served; this enables

interpretation of all content as UTF-8 by default. To use the

default browser choice (ISO-8859-1), or to allow the META tags

in HTML content to override this choice, comment out this

directive:

# AddDefaultCharset UTF-8

# # 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. # MIMEMagicFile conf/magic

Customizable error responses come in three flavors:

1) plain text 2) local redirects 3) external redirects

Some examples:

ErrorDocument 500 "The server made a boo boo."

ErrorDocument 404 /missing.html

ErrorDocument 404 "/cgi-bin/missing_handler.pl"

ErrorDocument 402 http://www.example.com/subscription_info.html

EnableMMAP and EnableSendfile: On systems that support it,

memory-mapping or the sendfile syscall may be used to deliver

files. This usually improves server performance, but must

be turned off when serving from networked-mounted

filesystems or if support for these functions is otherwise

broken on your system.

Defaults if commented: EnableMMAP On, EnableSendfile Off

EnableMMAP off

EnableSendfile on

Supplemental configuration

Load config files in the "/etc/httpd/conf.d" directory, if any.

IncludeOptional conf.d/*.conf What should I look for to confirm I am logged in as a admin? JPG xdmod.jpg (222 KB) Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

The image you sent does not appear to to be logged in. I sent an example to show what you would expect. You should see "Hello, " when signed in and the "Admin Dashboard" button if you're an admin. Also there is "[Developer]" if applicable, but you probably don't need to set yourself as a developer.

I'm not an expert in Kubernetes/OpenShift so I'm not sure if that could be causing the issue. Is this a reverse proxy or something similar? If that's the case then you may need to make sure all the necessary headers are being passed. Check if a cookie is being set. Look for PHPSESSID and xdmod_token. You can check the cookies by inspecting the request headers or (in chrome) click the lock icon to the left of the URL then select Cookies.

Do you need to modify httpd.conf directly instead of putting the configuration in a separate file? The ordering may matter so you could also put all the Open XDMoD configuration at the bottom it might make a difference. Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr PNG open-xdmod-s... (24.7 KB) Jeffrey T. Palmer , said over 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

It appears that the lack of ssl/https is causing this issue. I'm not sure if there is a way around this without altering the code, but I'll bring it up with our team next week.

Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr Robert Bartlett Baron , said over 1 year ago Thanks for letting me know that it might be the lack of ssl.

Robert Bartlett Baron , said about 1 year ago Just curious, was there anything that the team suggested when you brought this up? Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

We can supply you with a patch to disable the secure cookie. Otherwise, we plan to continue to keep everything as secure as possible by default.

Jeff

Ok, send me the patch.

Rob. Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

See attached. You can either use the patch command or just edit /usr/share/xdmod/libraries/rest.php directly. It's a very small change.

patch -p1 -d/usr/share/xdmod < 0001-Disable-secure-cookies.patch

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr 0001-Disable... (694 Bytes) Robert Bartlett Baron , said about 1 year ago Thanks

Robert Bartlett Baron , said about 1 year ago Was finally able to try this, and couldn't make it work.

Do I need to do anything to refresh any caches after editing the file? Last time I worked with PHP (some 20 years ago now), caching was the bane of my existence.

Rob. Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

If you have op caching enabled you will need to restart apache. I think that should be enough, but let us know if it still doesn't work.

Jeff

How would you recommend that I debug this issue. I am certain that this is not a caching issue.

Rob. Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Are you still seeing the same behavior as before (screen flashes then you are still logged out)? Is the cookie being set (Click the icon next to the URL then Cookies)? Try clearing all cookies for the domain and try again.

If everything looks fine try this:

Please follow these steps on Chrome: Open your Open XDMoD portal in the browser Open the developer tools (ctrl+shift+i) Click the "Network" tab Sign in to Open XDMoD Network tab should now have "login" "/rest/v0.1/auth" in the list, click that This should open a panel to the right, click the "Response" tab in that panel Send me the contents of the response If you don't use Chrome let me know what browser you use and I can put together similar instructions.

Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

I found some more notes about this issue and the problem then was with browser caching so please do try clearing your browser cache or using a different browser to see if you can reproduce the issue.

Jeff

Cookie “xdmod_token” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite xdmod-xdmod.apps.ocp-staging.massopen.cloud main_tab_panel#tg_summary xdmod-xdmod.apps.ocp-staging.massopen.cloud:23:21 Cookie “PHPSESSID” has been rejected because a non-HTTPS cookie can’t be set as “secure”.

It seems that I am able to log in, but the cookies are not being stored by the browser.

Any suggestions?

Rob. Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert, I'm unable to reproduce your issue in either Chrome or Firefox. I'm not really sure why it works for me and not you, but I did find another file that needs to be patched (/usr/share/xdmod/libraries/security.php):

--- a/libraries/security.php +++ b/libraries/security.php @@ -16,7 +16,7 @@ function start_session() $cParams["lifetime"], $cParams["path"], $cParams['domain'],

true
false ); @session_start(); } That should fix the PHPSESSID issue.
The documentation for SameSite appears to indicate that this might be a problem in future browser versions. If it is a problem now you can try to adjust your apache configuration with: Header always edit Set-Cookie (.*) "$1; SameSite=Lax" (See https://stackoverflow.com/questions/39750906/php-setcookie-samesite-strict#answer-51128675) Let me know if that works for you. Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr Robert Bartlett Baron , said about 1 year ago Ok, I am now able to log in to xdmod. We can close this ticket.

Jeffrey T. Palmer , said about 1 year ago Ticket: https://help.xdmod.org/support/tickets/29883

Hi Robert,

Great to hear you are able to log in now. Let us know if you have any other new issues.

Thanks, Jeff

Jeffrey T. Palmer Scientific Programmer Center for Computational Research 701 Ellicott Street Buffalo, NY 14203 716 881 7567 jtpalmer@buffalo.edu buffalo.edu/ccr This ticket has been Closed | about 1 year ago Reply

CCI-MOC / xdmod-cntr

xdmod ticket #29883 cannot log in with created admin account #208

======================================================================== Create Admin User

This is the main Apache HTTP server configuration file. It contains the

configuration directives that give the server its instructions.

See <URL:http://httpd.apache.org/docs/2.4/> for detailed information.

In particular, see

<URL:http://httpd.apache.org/docs/2.4/mod/directives.html>

for a discussion of each configuration directive.

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.

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 'log/access_log'

with ServerRoot set to '/www' will be interpreted by the

server as '/www/log/access_log', where as '/log/access_log' will be

interpreted as '/log/access_log'.

ServerRoot: The top of the directory tree under which the server's

configuration, error, and log files are kept.

Do not add a slash at the end of the directory path. If you point

ServerRoot at a non-local disk, be sure to specify a local disk on the

Mutex directive, if file-based mutexes are used. If you wish to share the

same ServerRoot for multiple httpd daemons, you will need to change at

least PidFile.

Listen: Allows you to bind Apache to specific IP addresses and/or

ports, instead of the default. See also the

directive.

Change this to Listen on specific IP addresses as shown below to

prevent Apache from glomming onto all bound IP addresses.

Listen 12.34.56.78:80

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.

Statically compiled modules (those listed by `httpd -l') do not need

to be loaded here.

Example:

LoadModule foo_module modules/mod_foo.so

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.

It is usually good practice to create a dedicated user and group for

running httpd, as with most system services.

'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

definition. These values also provide defaults for

any containers you may define later in the file.

All of these directives may appear inside containers,

in which case these default settings will be overridden for the

virtual host being defined.

ServerAdmin: Your address, where problems with the server should be

e-mailed. This address appears on some server-generated pages, such

as error documents. e.g. admin@your-domain.com

ServerName gives the name and port that the server uses to identify itself.

This can often be determined automatically, but we recommend you specify

it explicitly to prevent problems during startup.

If your host doesn't have a registered DNS name, enter its IP address here.

Deny access to the entirety of your server's filesystem. You must

explicitly permit access to web content directories in other

blocks below.

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.

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.

Relax access to content within /var/www.

Allow open access:

Further relax access to the default document root:

Possible values for the Options directive are "None", "All",

DirectoryIndex: sets the file that Apache will serve if a directory

is requested.

The following lines prevent .htaccess and .htpasswd files from being

viewed by Web clients.

ErrorLog: The location of the error log file.

If you do not specify an ErrorLog directive within a