Back to HTTPServer Main Index
A replacement URL which is used if "/" or an empty URL is requested.
You can specify an arbitrary request URL,
i.e. either a file in a FileService or any other services URL.
The default is "/Home", which links to a corresponding service.
Typically, some homePageService is linked to "/Home".
(The default setup registers the "Demos::WebHomePageForSTX" service under the "/Home" url).
If no HomeURL is specified, the server will respond with a
"404 'Not Found'" error response for requests with an empty URL.
A URL which is used if a link cannot be resolved, i.e.
if a nonEmpty, but bad name, bad suffix or bad directory was requested.
This can be used to lead the web-user back to the home page,
or to reply with some 'You bad-bad guy...' message
If left unspecified, the server will respond with a
"404 'Not Found'" error response.
Enable/disable tracing
e.g. request- and response-headers are traced on the Transcript.
Enable/disable error tracing
e.g. errors are traced on the Transcript.
Enable/disable data tracing
e.g. request- and response-data is traced on the Transcript.
Enable/disable debugging.
If enabled, and any error occurs in the Server, while processing a request,
the system enters the Smalltalk Debugger.
>BR>
If the server runs as standalone application,
(without GUI), a MiniDebugger (line-by-line debugger) is entered.
If disabled, errors are reported towards the webUser, and a
"500 'Internal Server Error'" response is generated
(with walkback informtion in the text-body).
Defines the maximum number of kept alive connections.
That is the number of socket connections and possible handler threads
that can be active at one time.
Defines the time (in seconds) after which inactive kept-alive connections are shut down.
Defines the time (in seconds) that temporary links are valid.
Temporary links are objects that will be stored under temporaryObjectNames
(for example internally generated bitmap images).
These temporary objects will be removed after that time.
This might be removed in the future, as individual services should care for any
temporary, synthetic links for themself and a global (server-wide) expiration time
is probably too coarse.
A reply-presenter is used to postprocess any HTML-output as generated by the http services.
These representers can be used to wrap all generated text into a common-looking page layout,
add decorators, backgrounds etc.
Reply representors are specified both per-service and, as a fall-back, globally here in the server settings.
For the reply presenter configuration of individual services, see Service Configuration.
This dialog presents a list of all reply-presenter classes (subclasses of ReplyPresenter) to
choose from. If you add your own subclass, this will be listed here as well.
By default, a presenter is used, which leaves the generated pages untouched (the "empty" reply presenter).
- EmptyDocumentReplyPresenter - the generated text is wrapped into the body part of a legal html document.
- ExeptReplyPresenter - The generated text is wrapped into a simple eXept presentation frame.
Take this as an example for your own representers.
- PlainReplyPresenter - the generated text is sent "as-is" (not even head and body are generated).
Bring server into and out of the maintenance mode
In maintenance mode, only requests from maintenance users are served
Useful if you want to restart services or change the server settings
and want to avoid web-access during this time (especially if the configuration
is in a non-consistent state for some time period).
All requests from other useres will get a "maintenance mode - retry later" response.
Starts the servers service process.
Stops the server (soft stop).
No new incoming connection requests are served,
and no new requests on kept-alive connections are handled.
All ongoing request processing
is finished and the requests are answered.
When all ongoing requests have been answered,
the servers service process is finally terminated,
and the accepting socket (server port) is closed.
Hard terminate the server
Immediately terminates any server activity (without giving ongoing requests
a change of being finished), stop the processes and close the server socket.
Useful if the server hangs on a request or entered some fatal error condition
(typically, due to software bugs ;-) so that a soft stop does not work.
Remove the server from settings dialog.
This frees all configuration and data objects associated to that server.
Save all the server settings into a file.
Useful if you want remember the configuration of a server
or to create a settings file for a standalone webServer.
Load all settings for this webServer from a previously saved settings file.
Remove a settings file from file system.
Copyright © 2003 eXept Software AG, all rights reserved
Doc $Revision: 1.4 $ $Date: 1997/08/07 15:06:09 $