WEBCIT for the Citadel System
- Copyright (C) 1996-2011 by the authors. Portions written by:
+ Copyright (C) 1996-2012 by the authors. Portions written by:
Art Cancro
Wilfried Goesgens
Several command-line options are also available. Here's the usage for
the "webcit" program:
- webcit [-i ip_addr] [-p http_port] [-s] [-S cipher_suite] [-t tracefile]
+ webcit [-i ip_addr] [-p http_port] [-s] [-S cipher_suite]
+ [-g guest_landing_page]
[-c] [-f] [remotehost [remoteport]]
*or*
- webcit [-i ip_addr] [-p http_port] [-s] [-S cipher_suite] [-t tracefile]
+ webcit [-i ip_addr] [-p http_port] [-s] [-S cipher_suite]
+ [-g guest_landing_page]
[-c] [-f] uds /your/citadel/directory
Explained:
different port. If you do not specify a port number, WebCit will attempt
to use port 80.
- -> tracefile: where you want WebCit to log to. This can be a file, a
- virtual console, or /dev/null to suppress logging altogether.
+ -> The "guest landing page" is a location on your WebCit installation where
+ unauthenticated guest users are taken when they first enter the root of
+ your site. If guest mode is not enabled on your Citadel server, they will
+ be taken to a login page instead. If guest mode is enabled but no landing
+ page is defined, they will be taken to the Lobby.
-> The "-c" option causes WebCit to output an extra cookie containing the
identity of the WebCit server. The cookie will look like this: