Actions
Bug #11361
openWServer: confusion over the wtConfigurationFile argument, incorrect ISAPI WServer behavior
Start date:
02/22/2023
Due date:
% Done:
0%
Estimated time:
Description
There are two configuration files:
wt_config.xml
- the
wthttpd
file, only used by the wthttp connector
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:
- Better document these functions
- Fix constructor #2 and #3 for wtisapi
No data to display
Actions