Yes, you can. By default, the DWebPro primary Web server listens on the 127.0.0.1 IP address. Refer to the IP field in the Web Server tab for more information. With this configuration, you will be able to access the hosted Web site from the local machine only. To allow others on the LAN to access your DWebPro primary Web server, you have to configure it to listen on the LAN IP address of the machine on which DWebPro is running (for example, 192.168.0.1). You can achieve this in two ways.

• You can configure the DWebPro primary Web server with the specific IP address (for example, 192.168.0.1). Refer to the IP field in the Web Server tab for more information.

  [WebServer]
  IP=192.168.0.1

• You can configure DWebPro to listen on the 0.0.0.0 IP address:

  [WebServer]
  IP=0.0.0.0

  In this case, the primary Web server listens on all available IP addresses, including 127.0.0.1.

DWebPro does not use logging by default, however you can easily configure it to use its logging feature. To enable logging, use the Log Level and Log Path fields in the Web Server tab. For example, the following settings in http.ini set the logging level to short (1) and the location of the logs to the ##DWEBPRO_DOCUMENTROOT##\logs (C:\DWebPro\deploy\www\logs) folder.

[WebServer]
LogLevel=1
LogPath=##DWEBPRO_DOCUMENTROOT##\logs

Aliases specify folder aliases similar to those provided by Apache. When creating or maintaining aliases in http.ini, keep in mind that each alias=path pair must be separated by a pipe "|" character. The following example specifies a custom location for online documentation using the alias "/docs". Aliases can be defined using the Web Server tab of the DWebPro Configurator.

[WebServer]
Aliases=/docs=C:\web\documentation

Aliases are also dependent upon the DWebPro license in use. Please refer to the DWebPro Licensing Model topic for more information.

You can enable the directory listing feature by editing http.ini as shown below. This feature can also be enabled or disabled using the Web Server tab of the DWebPro Configurator.

[WebServer]
DirectoryListing=1

Setting this field to 0 disables the directory listing feature. When the directory listing feature is disabled and the browser navigates to a directory that does not contain a default document, the 404 Not Found page displays.

The rewrite engine is enabled in the [WebServer] portion of http.ini. This feature can also be enabled or disabled using the Web Server tab of the DWebPro Configurator. The following example enables the rewrite engine and directs DWebPro to use the rewrite.ini rules file located at ##DWEBPRO_DOCUMENTROOT##.

[WebServer]
RewriteEngine.Start=1
RewriteEngine.FileName=##DWEBPRO_DOCUMENTROOT##\rewrite.ini
RewriteEngine.ReloadOnEveryRequest=0

As an example of redirecting Web traffic to a particular set of files (in this case, the "/docs" location), we can create the following rule in rewrite.ini:

# This is a sample of the Rewriting Engine usage
RewriteCond %{REMOTE_ADDR}  127\.0\.0\.1 [OR]
RewriteCond %{REMOTE_HOST}  ^localhost*
RewriteRule  ^.*?/(\d*?)$   /docs/index.html

You can test your rewrite rules using the Rewrite Engine Tester tool, which is located under the DWebPro Utilities Program Group.

The URL rewrite engine provides a subset of the Apache mod_rewrite module. For more information on the Apache mod_rewrite module, refer to http://httpd.apache.org/docs/2.0/mod/mod_rewrite.html and http://httpd.apache.org/docs/2.0/misc/rewriteguide.html.