WebSEAL server log errors

Due to the nature of RPC over HTTP, socket errors might be printed in the WebSEAL server log. The server-log-cfg configuration entry in the [logging] stanza specifies the logging agent configuration.

For example:

2010-10-26-05:45:25.836+10:00I----- 0x38AD5424 webseald ERROR wiv socket 
WsSslListener.cpp 1737 0xafb3fb90
DPWIV1060E   Could not read from socket (406)
2010-10-26-05:45:25.838+10:00I----- 0x38AD5425 webseald ERROR wiv socket 
WsSslListener.cpp 1658 0xafb3fb90
DPWIV1061E   Could not write to socket (406)

These error messages are expected when request/response streaming is active and the connection is closed before the full content-length has been received.

We can turn off these error messages by setting the suppress-client-ssl-errors in the [ssl] stanza of the WebSEAL configuration file to true. See Specify the WebSEAL host name for details about the location of this configuration file.

Parent topic: Microsoft RPC over HTTP

Related concepts

• RPC over HTTP support in WebSEAL
• Junction configuration
• POP configuration
• Authentication limitations
• Timeout considerations
• Worker thread consideration