proxying rtmpt by nginx
just starting
just.starting at gmail.com
Sat May 31 23:43:58 MSD 2008
Thanks Rajesh for the quick reply.
I searched the net quite a bit for the solution to my question and come up
with the link : http://marc.info/?l=nginx&m=121180411000488&w=2
Can you please explain this:
1. /open/, /close/, /send/,/idle/ are the server path used in rtmpt
queries to the rtmpt server. I mean are the paths generic.
2. Will these paths cover all rtmpt queries. Any pointer or link will be
must helpful.
Thanks
Rakesh.
On Sat, May 31, 2008 at 8:40 PM, Rajesh Dharmalingam <
rajesh.dharmalingam at gmail.com> wrote:
> Yes it is possible.
>
> location /open/ {
> proxy_pass http://127.0.0.1:8088;
> proxy_redirect off;
> proxy_set_header X-Forwarded-For
> $proxy_add_x_forwarded_for;
>
> client_max_body_size 10m;
> client_body_buffer_size 128k;
>
> proxy_connect_timeout 90;
> proxy_send_timeout 90;
> proxy_read_timeout 90;
>
> proxy_buffer_size 4k;
> proxy_buffers 4 32k;
> proxy_busy_buffers_size 64k;
> proxy_temp_file_write_size 64k;
>
> include conf/fastcgi_params;
> }
>
> Similar to this is for /close/ , /idle/ , /send/.
>
>
> Add this and it will work.
>
>
> On Sat, May 31, 2008 at 7:52 PM, just starting <just.starting at gmail.com>
> wrote:
>
>> hi,
>>
>> Is it possible to run red5 rtmpt via proxy of nginx?
>>
>> I know that the protocols are different, but still, is there any
>> workaround available?
>>
>> Thanks,
>> Rakesh.
>>
>
>
>
> --
> Regards,
> -Rajesh
>
> "Stick to our roots and not to forget where we come from"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://nginx.org/pipermail/nginx/attachments/20080601/d8cfee66/attachment.html>
More information about the nginx
mailing list