# \*-log - 4xx response from Kong are not logged #892

**URL:** <https://discuss.konghq.com/t/log-4xx-response-from-kong-are-not-logged-892/95>\
**Category:** Feature Requests & Feedback\
**Created:** [November 28, 2017, 11:33pm UTC](https://discuss.konghq.com/t/log-4xx-response-from-kong-are-not-logged-892/95 "2017-11-28T23:33:10Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![CaesarKing](https://yyz2.discourse-cdn.com/flex036/user_avatar/discuss.konghq.com/caesarking/32/36_2.png) [@CaesarKing](https://discuss.konghq.com/u/CaesarKing)\
**Post date:** [November 28, 2017, 11:33pm UTC](https://discuss.konghq.com/t/log-4xx-response-from-kong-are-not-logged-892/95/1 "2017-11-28T23:33:10Z")

</div>

when Kong responds in a 4xx (e.g. 401, 403) the logging plugins (all \*-log and Galileo) are not logging those requests. This might affect runscope as well.

See GitHub Issue:  
[\*-log - 4xx response from Kong are not logged #892](https://github.com/Kong/kong/issues/892)