Dwarf HTTP Server 1.3.3

Upgrading

Content

• Version 1.2.x to 1.3.0
• Version 1.1 to 1.2.0
• Version 1.0.1 to 1.1
• Version 1.0 to 1.0.1

Version 1.2.x to 1.3.0

• you must upgrade the base Dwarf framework to version 1.3.x

Version 1.1 to 1.2.0

XML Configuration:

• change the LOG_HTTP logging levels to LOG_XFER, which is now used to generate the HTTP transfer logs

Version 1.0.1 to 1.1

XML Configuration:

• remove the DefaultServlet, ResourceServlet and InfoServlet references
• use the ExtendedLogFormat instead of the W3CExtendedLogFormat
• update the logging configuration to match the default ExtendedLogFormat behavior (it logs the "Host" header and the remote user name by default)
• use the DwarfLogFormat instead of the DefaultLogFormat
• any default servlet must be now mapped to the "/" pattern
• remove the SK.gnome.dwarf.utils.Cache instances from all Application objects
• move the defaultEncoding and forceAuthentication attributes from the HTTPParameters to the particular Application instance
• if you are using one of the mimeTypes, encodings, charsets or errorCodes attribute of the HTTPParameters, you must change the URLs of the default property files, which now reside in the "conf/samples/http/" directory.
• all parameters in the HTTPParameters class now have reasonable defaults; the instance is added to the HTTPServer automatically if it is not done explicitly, therefore it may be omitted from the default configuration

Development:

• the Request object always returns a valid input stream from the getInputStream() method if the getReader() method has not been called previously

Version 1.0 to 1.0.1

• defaultEncoding HTTP parameter now accepts MIME charsets instead of the Java encoding names. For example, if you were using ISO8859_1, you should use now ISO-8859-1 instead.

Return to the main page.