Danny B. wrote:

is there ZWS configuration available to view somewhere?

I'm particularly looking for things like list and order of default documents (directory indexes) and content types ATM, but I think it would be useful to have such relevant configuration settings which have direct influence on behavior written somewhere if it's not yet, maybe https://wiki.toolserver.org/view/ZWS/Default_config or so... However, if it already exists, please navigate me, thanks.

Your vague e-mail makes it kind of difficult to respond to. What are you trying to do? What is or isn't working?

The user guide for Zeus Web Server is available in PDF here: http://support.zeus.com/zws/media/docs/ZWSUserGuide.pdf

There are also some helpful documents on the wiki related to ZWS, but you've likely already found those.

If you log in to a web server and look in /opt, that's where the configuration for zeus is stored, I believe. I don't see much in /opt/zeus/admin/global.cfg, for example, but I'm also not sure what you're looking for, so it makes it much more difficult to find.

MZMcBride

-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1

In article 92048.20224.24006-8740-1034033847-1297358348@email.cz, Danny B. Wikipedia.Danny.B@email.cz wrote:

is there ZWS configuration available to view somewhere?

No.

I'm particularly looking for things like list and order of default documents (directory indexes)

The current list of index files is: index.html, index.htm, index.shtml, index.cgi, index.php, index.fcgi

You really shouldn't rely on that particular order, though. There's no guarantee that the order won't change in future, and I can't imagine any situation where you need to have both "index.html" and "index.fcgi" (for example) in the same directory.

and content types

A comprehensive list of type<>extension mappings is available at /etc/opt/ts/apache/2.2/mime.types. If any of these are missing in ZWS, you can open a request in JIRA to have them added.

but I think it would be useful to have such relevant configuration settings which have direct influence on behavior written somewhere if it's not yet

This usually just results in out-of-date or incorrect documentation on the wiki, rather than any useful information. Major parts of the configuration (such as how PHP and FastCGI work) is already documented.

river.