DWebPro Stand Alone Web Server
Getting Started with DWebPro
What is DWebPro?
System Requirements
DWebPro Architecture
Compatibility Issues
ASP.NET Compatibility
ColdFusion Compatibility
ASP Classic 3.0 Support
The aspisapi.ini Configuration File
The Server.NewMail Object
The Server.Registry Object
The Request.Upload Object
Where to Obtain Technical Assistance
Changes since DWebPro 5.2
Configuring DWebPro
Add-On Packages
DWebPro Configurator Tabs
Main
Splash Screens
Browser
Web Server
SMTP Server
Server Side Languages
ASP.NET Server
CGI
ISAPI
ColdFusion
Tomcat
Zope
Railo
JBoss
Databases
MySQL
Firebird
SQLite
PostgreSQL
HSQLDB
Microsoft Access
Microsoft SQL Server Compact Edition
Microsoft SQL Server 2000 Desktop Engine
Microsoft SQL Server 2005 Express Edition
Oracle XE
ODBC
External Software
Directories
Windows Requirements
Warnings
Exception Log
Shutdown
Additional Tools
MDAC
Flash Player
Windows Installer
Acrobat Reader
.NET Framework
Advanced Features
Auto Update
The deploy Folder
Advanced Topics
Application Program Interface (API)
Command Line Parameters
Internal Constants
Interactive Install Workflow
Additional Tools
DWebPro Browser Software
My IE Software (My Internet Explorer)
Starter Software
Advanced Tools
DWebPro Re-Brander Software
Microsoft SQL Server 2005 Compact Edition Manager
URL Rewrite Engine
Multilanguage Support
DWebPro Translator Software
Security Tools
DWebPro License Bundler Software
DWebPro Encoder Software
Trial Generation
DWebPro Trial Generator Software
DWebPro Serial Generator Software
PHP Extensions
The php_dwebpro Extension
The php_registry Extension
DWebPro Service
Frequently Asked Questions
General FAQs
Primary Web Server FAQs
Browser FAQs
ASP.NET FAQs
PHP and MySQL FAQs
ASP Classic 3.0 and Microsoft Access FAQs
Licensing FAQs
Purchasing FAQs
HOWTOs / Tutorials
How To Create Your CD/DVD
How To Read DWebPro Internal Constants From Code
How To Distribute a PHP/MySQL Web Site With DWebPro
How To Distribute ASP Classic 3.0/Microsoft Access Web Site With DWebPro
How To Use Microsoft Access Database On CD/DVD
How To Test a DWebPro Project Without Burning CDs/DVDs
Virtual CD-ROM Control Panel Setup
Create the ISO image
Activate the ISO image
How To Create An Install Package With DWebPro
How To Test Your Install Packages With The FREE License
How To Protect Your License From Stealing With The DWebPro License Bundler
How To Protect Your PHP and ASP Classic 3.0 source Code From Stealing With The DWebPro Encoder
How To Translate The DWebPro Interface
How To Personalize The HTTP Error Messages
How To Create A Trial Version Of Your Web Applications With DWebPro
How To ReBrand DWebPro With A DWebPro ReBrand License
How To Test Your mod_rewrite Directives With The Rewrite Engine Tester
License
DWebPro Licensing Model
Limitations of the Free License
DWebPro EULA
Copyright Notes

DWebPro Is The Best Stand Alone Web Server On The Market!!!

DWebPro Is The Best Stand Alone Web Server On The Market!!!

Partecipa al corso operativo "Come Vendere Con Successo il Tuo Software Su Internet" vendere-software-su-internet.it

Partecipa al corso operativo "Come Vendere Con Successo il Tuo Software Su Internet" vendere-software-su-internet.it

Partecipa al corso "Mastering Landing Pages" masteringlandingpages.com

Partecipa al corso "Mastering Landing Pages" masteringlandingpages.com

Primary Web Server FAQs

Can I use DWebPro as an Intranet server (for example, on a LAN)?

 

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.

 

How to enable logging features?

 

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
 

How can I use aliases?

 

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.

 

How can I enable/disable directory listings?

 

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.

 

How can I enable/disable the rewrite engine?

 

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.


DWebPro Is The Best Stand Alone Web Server On The Market!!!

DWebPro Is The Best Stand Alone Web Server On The Market!!!

Partecipa al corso operativo "Come Vendere Con Successo il Tuo Software Su Internet" vendere-software-su-internet.it

Partecipa al corso operativo "Come Vendere Con Successo il Tuo Software Su Internet" vendere-software-su-internet.it

Partecipa al corso "Mastering Landing Pages" masteringlandingpages.com

Partecipa al corso "Mastering Landing Pages" masteringlandingpages.com
Prev Page Prev Page