Help with Request Logging Profile "Respond on error" setting

Hello,

I have a question about Request Logging profile in reference to the "Respond on Error" setting.

As I understand this profile is intended only for logging and shouldn't interfere with the normal operation of the Virtual Server where it's applied to. But when we tried to use it, the behaviour was a little weird. With the setting disabled, when the server responded a HTTP400 error, the browser's client, instead of getting the same error, not even displayed the web page from the server, the error was simply a "NET REFUSED" message.

I couldn't perform more troubleshooting as it was in a production environment but that I'm trying to clarify is: do I need to enable the "Respond on Error" setting to allow the HTTP server error to be displayed to the client? I tend to understand just the opposite: setting disabled -> do nothing, setting enabled -> respond something different than the server.

Those are our profile settings

app-service none

defaults-from /Common/request-log
log-request-logging-errors no
log-response-by-default yes
log-response-logging-errors disabled
proxy-close-on-error no
proxy-respond-on-logging-error no
proxy-response none
request-log-error-pool none
request-log-error-protocol mds-udp
request-log-error-template none
request-log-pool /Common/pool_Syslog
request-log-protocol mds-udp
request-log-template "$DATE_NCSA $CLIENT_IP $RESPONSE_MSECS $SERVER_IP $SERVER_PORT $HTTP_REQUEST $HTTP_STATUS $RESPONSE_SIZE ${User-agent}"
request-logging enabled
response-log-error-pool none
response-log-error-protocol mds-udp
response-log-error-template none
response-log-pool /Common/pool_Syslog
response-log-protocol mds-udp
response-log-template "$DATE_NCSA $CLIENT_IP $RESPONSE_MSECS $SERVER_IP $SERVER_PORT $HTTP_REQUEST $HTTP_STATUS $RESPONSE_SIZE ${User-agent}"
response-logging enabled

Thanks.