search for: proxy_buffering

Hi all, I want to do a proxy to icecast (:8000) with nginx (:80). Its working for me, stream is running on port 80, but on the first loading is "pending" For a long time before its starts play. Who using the "proxy_pass" on nginx and can help? Thnx. -------------- next part -------------- An HTML attachment was scrubbed... URL:

Thank you all. Except from the buffering it was the fact that I used "localhost" instead of 127.0.0.1 in the proxy_pass. Now my configuration is: location /stream1/ { proxy_buffering off; proxy_ignore_client_abort off; proxy_intercept_errors on; proxy_next_upstream error timeout invalid_header; proxy_redirect off; proxy_set_header X-Host $http_host; proxy_set_header...

We've tested this as working relatively well, disable buffering is the major key if I recall. Otherwise the NGINX server loads up data before handing off to the client. server { listen 80; server_name my_dns_name.tldn; location / { proxy_buffering off; proxy_ignore_client_abort off; proxy_intercept_errors on; proxy_next_upstream error timeout invalid_header; proxy_redirect off; proxy_set_header X-Host $http_host; proxy_set_header...

Hi! I've been giving support for streaming and streamcasting over HTTPS... Everything started while giving streaming support to my website. When I read a console error (or was it a warning?) on Chrome, when the browser accessed to an http:// resource from an https:// domain. Then I decided to fix it by the clean way. I don't need official support yet... but if you don't mind to

Streaming works with Unicorn + Apache. Both with and without deflating. My understanding is that Unicorn + Apache is not a good combination though because Apache does not buffer, and thus Unicorn has no fast client in front. (I don''t know which is the ultimate technical reason Unicorn puts such an emphasis on fast clients, but will do some research about it.) I have seen in

...n! My predicament is complicated to explain :- ) The only I want to share is a full HTTPS solution for icecast-server... El 13/03/2019 a las 17:47, Adrian Pardini escribió: > Hi Abel, I'm not quite sure I understand your predicament here. > > We settled for using our main nginx with proxy_buffering off for the > media files. That way certbot takes care of it too. > > Regards > > On Wed, 13 Mar 2019 at 13:36, Abel Romero <romeroperezabel at gmail.com> wrote: >> Hi! >> >> I've been giving support for streaming and streamcasting over HTTPS... >> &...

Hi Abel, I'm not quite sure I understand your predicament here. We settled for using our main nginx with proxy_buffering off for the media files. That way certbot takes care of it too. Regards On Wed, 13 Mar 2019 at 13:36, Abel Romero <romeroperezabel at gmail.com> wrote: > > Hi! > > I've been giving support for streaming and streamcasting over HTTPS... > > Everything started while givin...

G''day I''m just wondering if anybody knows of a way to get mongrel_upload_progress working with nginx? I''ve had a fair bit of a look around but havn''t been able to come up with anything, yet. -- - James -------------- next part -------------- An HTML attachment was scrubbed... URL:

I have strange error that happens after couple of hours. Some instances start to respond on any request with status code 500. Log file unicorn.stderr.log gets populated with this error: app error: undefined method `each'' for nil:NilClass (NoMethodError) /usr/local/lib/ruby/gems/1.9.1/gems/rack-1.1.2/lib/rack/utils.rb:267:in `initialize''

I am using mongrel_cluster with mod_proxy_balancer and would like to enable compression (assuming it improves throughtput) and limit file size upload. I configured mod_deflate and LimitRequestSize in Apache, but in my trials looks like the proxied calls bypass those directives (the conf goes below). Is there a way to get this? -- fxn # Adapt this .example locally, as usual. # # To be

Hi, Im using nginx and rails for my site which contains url with georgian letters ie განცხადებები so something like http://gancxadebebi.ge/ka/%E1%83%92%E1%83%90%E1%83%9C%E1%83%AA%E1%83%AE%E1%83%90%E1%83%93%E1%83%94%E1%83%91%E1%83%94%E1%83%91%E1%83%98 It is mainly working perfectly but sometimes I receive request with truncated url ie 1 -

Hi All, I am setting up puppetmaster with nginx and passenger and separating the Puppetmaster primary CA server. I have 3 host loadbalancer01 - Nginx doing LB on IP address and also running puppetmaster with passenger under 127.0.0.1 (port 8140). primaryca - Puppetmaster Primary CA pclient - Puppet Client The did the following steps: On Primary CA server: ---------------------------- cd

We''ve been running unicorn-3.6.2 on REE 1.8.7 2011.12 in production for quite some time and we use monit to monitor each unicorn worker. Occasionally, I''ll get a notification that a worker has timed-out and has been re-spawned. In all these cases, when I look at the rails logs, I can see the last request that the worker handled, and they all have appeared to complete