Wilma Operation Modes
On Wilma's main page the main operation mode of Wilma can be set.
The operation mode of Wilma specifies how Wilma's routing engine - the part that decides on how to react on an incoming HTTP/HTTPS request - should work.
In this case - routing engine shall not evaluate anything on the request, the request always should be routed to the proxy path. This means in this operational mode Wilma acts as a pure transparent proxy, without the stubbing part
In this case - routing engine evaluates the incoming request normally (by using the Stub Configuration), and works normally, - but in case the message should be handled in proxy mode (i.e. there is no such Stub config that could be used to generate the response), Wilma responds with E404 (text/html/xml) error message.
In this case - Wilma works in normal, i.e. "mixed" mode, this is the default operational mode - routing engine evaluates the incoming request, and based on the stub configuration, either a stub answer is generated, or proxy mode is used
Note: In case WilmaBypass=true parameter-value appears in the incoming request header, Wilma should handle the message in proxy mode (so no dialogDescriptor evaluation is performed at all). This works this way even if Wilma is in exclusive STUB mode.