(52) Empty reply from server

[Francis Daly]

On Wed, Apr 20, 2016 at 12:54:13PM +0530, Pankaj Chaudhary wrote:

Hi there,

> >>But your code snippet does not match exactly the types and return values
> >>of that example. I don't know if that is something worth investigating.
> 
> I have tried to change match exactly the types and return values
> of that example. but below is response curl: (52) Empty reply from server

> ngx_int_tset_custom_header_in_headers_out(ngx_http_request_t *r,
> ngx_str_t *key, ngx_str_t *value) {
<snip>

The code snippet you show seems to relate to writing your own http
headers.

> below is "curl -i" response
> 
> HTTP/1.1 200 OK
> Server: nginx/1.9.12
> Date: Wed, 20 Apr 2016 15:25:20 GMT
> Content-Type: text/plain
> Content-Length: 14
> Connection: keep-alive
> cookie: thisitestvalue
> user_agent: 10.9 user
> get-rese: Cookie

The "curl" output you show seems to show your own http headers being
successfully written.

So it looks like what you have shown, is working.

That's good.

	f
-- 
Francis Daly        francis at daoine.org