# Request\_completion variable and zero length 200 response

**URL:** <https://www.ruby-forum.com/t/request-completion-variable-and-zero-length-200-response/193975>\
**Category:** NGINX\
**Created:** [August 27, 2010, 12:19pm UTC](https://www.ruby-forum.com/t/request-completion-variable-and-zero-length-200-response/193975 "2010-08-27T12:19:13Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![SS\_SSSSSSSSSS\_S](https://www.ruby-forum.com/letter_avatar_proxy/v4/letter/s/b19c9b/32.png) [@SS\_SSSSSSSSSS\_S](https://www.ruby-forum.com/u/SS_SSSSSSSSSS_S)\
**Post date:** [August 27, 2010, 12:19pm UTC](https://www.ruby-forum.com/t/request-completion-variable-and-zero-length-200-response/193975/1 "2010-08-27T12:19:13Z")

</div>

Hello,

We are using request\_completion core variable to log every request.  
Until  
recently, we found that some requests got logged with:

$request\_completion = NULL  
$statue = 200  
$bytes\_send = 0  
$body\_bytes\_send = 0

so the question is in what condition, will nginx set request\_completion  
to  
NULL while at the sam time set status to 200 with zero bytes send? Is  
this a  
client-side problem or nginx’s bug?

Below is a sample log(request\_completion is the last field and it’s  
NULL):  
[27/Aug/2010:18:15:43 +0800] 114.139.50.115 GET /LoginFrame.asp  
61.172.242.15:80 [Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1;  
SV1;  
GTB6.5; .NET CLR 1.1.4322)] HTTP/1.1 200 0 0