wandenberg
commented
12 years ago Hi,
which version of nginx and push-stream module are you using? Can you send me a way how to reproduce the problem?
Which client are you using? The responsibility of parse the response must be of the client, not yours :)
Regards, Wandenberg
On Mon, Aug 20, 2012 at 2:45 AM, Terry.Mao notifications@github.com wrote:
the http response get 200 status, everythng gonaa all right , but somethimes the response like the format:
chunk-size \r\n chunk-data\r\n .....
0\r\n
i know this is the http 1.1 transfer-encoding : chunked
but the issue is that i got the reponse without chunk-size sometimes
like :
chunk-data \r\n chunk-data \r\n.
it's hard to parse the response for client.
my nginx config file:
push_stream_shared_memory_size 300M; push_stream_shared_memory_cleanup_objects_ttl 30s; push_stream_message_ttl 72h; push_stream_max_messages_stored_per_channel 20; chunked_transfer_encoding on; chunkin on;
server { listen 61.147.75.31:80; listen 112.84.189.31:80; charset utf-8; access_log /data/logs/nginx/notify.log; keepalive_timeout 300;
location ~ /sub/(.*) { set $push_stream_channels_path $1; push_stream_subscriber long-polling; push_stream_authorized_channels_only off; push_stream_content_type text/plain; push_stream_subscriber_connection_ttl 300s; push_stream_longpolling_connection_ttl 300s; }
error_page 411 = @my_411_error;
location @my_411_error { chunkin_resume; }
}
server { listen 192.168.1.15:80; charset utf-8; access_log /data/logs/nginx/notify.log; keepalive_timeout 300;
location /pub { push_stream_publisher admin; set $push_stream_channel_id $arg_channel; push_stream_store_messages on; push_stream_keepalive on; }error_page 411 = @my_411_error; location @my_411_error { chunkin_resume; }
}
— Reply to this email directly or view it on GitHubhttps://github.com/wandenberg/nginx-push-stream-module/issues/45.
MysqlProxy
Terry-Mao
the http response get 200 status, everythng gonaa all right , but somethimes the response like the format:
chunk-size \r\n chunk-data\r\n .....
0\r\n
i know this is the http 1.1 transfer-encoding : chunked
but the issue is that i got the reponse without chunk-size sometimes
like :
chunk-data \r\n chunk-data \r\n.
it's hard to parse the response for client.
my nginx config file:
push_stream_shared_memory_size 300M; push_stream_shared_memory_cleanup_objects_ttl 30s; push_stream_message_ttl 72h; push_stream_max_messages_stored_per_channel 20; chunked_transfer_encoding on; chunkin on;
server { listen 61.147.75.31:80; listen 112.84.189.31:80; charset utf-8; access_log /data/logs/nginx/notify.log; keepalive_timeout 300;
}
server { listen 192.168.1.15:80; charset utf-8; access_log /data/logs/nginx/notify.log; keepalive_timeout 300;
}