ONLINE HELP
 WINDEVWEBDEV AND WINDEV MOBILE

This content has been translated automatically.  Click here  to view the French version.
Help / Developing an application or website / WEBDEV specific features / WEB server
  • Overview
WINDEV
WindowsLinuxJavaReports and QueriesUser code (UMC)
WEBDEV
WindowsLinuxPHPWEBDEV - Browser code
WINDEV Mobile
AndroidAndroid Widget iPhone/iPadIOS WidgetApple WatchMac Catalyst
Others
Stored procedures
Type and version of Web server
Overview
The configuration diagnostics displays the following error: "HTTP Server: Version "
This error indicates that a problem was detected regarding the Web server.
This error is displayed in the following cases:
  • The connection is refused.
    • No Web server is installed locally or the Web server is not started.
      Solution: Install, configure and start a Web server on the local workstation. This allows you to check the sites created with WEBDEV locally.
    • The Web server is not listening on port 80.
      Solution: By default, Web servers listen on port 80. WEBDEV tries to connect onto port because there is no specific configuration.
      If the Web server is not listening on this port, you need to add the port in the WEBDEV administrator's "Advanced" tab, "Host name/IP" option: after the host name/IP, you need to add the ":" character, followed by the port..
      The most common alternative ports of Web servers are 81 and 8080.
      For example, with the default host name "localhost", if the Web server is listening on port 81, the value becomes "localhost:81".
  • The connection is accepted but the response is invalid. This operating mode can correspond to one of the following cases:
    • A thrid-party program monopolizes (or locks) this port. The port was not available, the Web server is not accessible.
    • The Web server accepted the connection but it did not respond (or it did not respond fast enough).
  • The detected Web server is not the one specified in the WEBDEV administrator ("Advanced" tab, "Server" button).
    Solution: Most often, in this case, an inversion between IIS and Apache explains the error (e.g. when using both servers alternately to run tests)..
Reminder: Initial diagnosis
The first diagnostic consists in starting a browser and in connecting to http://localhost/ (localhost can be replaced with the proper host/IP with a port if necessary).
Usually:
  • IIS displays a page with a simple image containing IIS.
  • Apache displays "It works!".
Minimum version required
  • Version 15
Comments
Click [Add] to post a comment

Last update: 09/21/2024

Send a report | Local help