Project

General

Profile

Actions

Bug #11361

open

WServer: confusion over the wtConfigurationFile argument, incorrect ISAPI WServer behavior

Added by Roel Standaert about 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Target version:
Start date:
02/22/2023
Due date:
% Done:

0%

Estimated time:

Description

There are two configuration files:

WServer has three constructors:

WServer(const std::string& wtApplicationPath, const std::string& wtConfigurationFile = std::string()); // #1
WServer(int argc, char *argv[], const std::string& wtConfigurationFile = std::string()); // #2
WServer(const std::string& applicationPath, const std::vector<std::string>& args, const std::string& wtConfigurationFile = std::string()); // #3

In the case of #1 the wtConfigurationFile argument refers to wt_config.xml, in the case of #2 and #3 the wtConfigurationFile argument refers to wthttpd.

The documentation is not entirely clear on that. In fact, a mistake was made when implementing the ISAPI connector. When #2 or #3 are used with a configuration
file argument it will try to treat them as a wt_config.xml.

We'll need to:

  1. Better document these functions
  2. Fix constructor #2 and #3 for wtisapi

No data to display

Actions

Also available in: Atom PDF