Jump to content

Nginx return empty data, while header is 200 OK


Recommended Posts

I have a problem with my rest service as below:

 

 1. a server with NGinx, PHP-FPM, provide rest service: example: http://example.com/rest.php, this link only show content: 1001:Successfully

 2. another server using curl call this rest service to get content. With happy case, it must get content from rest service is 1001:Successfully. But problem happen -

In most case it get content ok, but sometimes I get empty content while http_status is 200 ok. I don't know what is happening. Could anyone help me?

 

Empty content and CURL debug information as below:

 

    '* About to connect() to example.com port 80 (#0)

    *   Trying xxx.xxx.xxx.xxx...

    * connected

    * Connected to example.com (xxx.xxx.xxx.xxx) port 80 (#0)

    > GET /rest.php HTTP/1.1

    User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; rv:1.7.3) Gecko/20041001 Firefox/0.10.1

    Host: example.com

    Accept: */*

    Accept-Encoding: deflate, gzip

    

    < HTTP/1.1 200 OK

    < Server: XXX

    < Date: Mon, 12 May 2014 12:58:17 GMT

    < Content-Type: text/html

    < Transfer-Encoding: chunked

    < Connection: keep-alive

    < 

    * Connection #0 to host channel.ssgroup.vn left intact

    * Closing connection #0

    ',

    )

Link to comment
Share on other sites

This thread is more than a year old. Please don't revive it unless you have something important to add.

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.