search for: proxy_set_head

It works well when I use webrick. The config of nginx is from puppet wiki, some logs is below, what''s wrong? puppet version:0.25.4 client: ... ... debug: /File[/var/lib/puppet/ssl/certs/ca.pem]: Autorequiring File[/ var/lib/puppet/ssl/certs] debug: /File[/var/lib/puppet/state/state.yaml]: Changing mode debug: /File[/var/lib/puppet/state/state.yaml]: 1 change(s) debug:

...le REMOTE_ADDR. When I do a <%= request.env["REMOTE_ADDR"] %> with pen balancing, it sends in the proper (and expected) 192.168.1.21. When nginx is the balancer, the output becomes: 192.168.1.21, 127.0.0.1. the nginx proxy information I have set is: proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; Just wondering if anyone else has run into this problem, and it''s possible solution. Thank you.

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:

...ALL:!ADH:RC4+RSA:+HIGH:+MEDIUM:-LOW:-SSLv2:-EXP; ssl_prefer_server_ciphers on; ssl_verify_client optional; ssl_verify_depth 1; access_log logs/loadbalancer01_access.log main; error_log logs/loadbalancer01_error.log; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Client-Verify $ssl_client_verify; proxy_set_header X-Client-DN $ssl_client_s_dn; proxy_set_header X-SSL-Subje...

...ALL:-ADH:+HIGH:+MEDIUM:-LOW:-SSLv2:- EXP; ssl_client_certificate /var/lib/puppet/ssl/ca/ca_crt.pem; ssl_verify_client on; root /var/empty; access_log /var/log/nginx/access-8140.log; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Client-Verify SUCCESS; proxy_set_header X-Client-DN $ssl_client_s_dn;...

Hi There, Im running an amazon instance with nginx proxying to a unicorn sock. For some reason, even though i specify the production environment, when being visited by nginx, the site shows errors in development form. Interestingly, when running on a port rather than a sock, if i visit that port, the errors are rendered as normal with a 500 page, the same port, throught nginx, shows errors

...authenticated and client without certs ssl_verify_client optional; # obey to the Puppet CRL ssl_crl /var/lib/puppet/ssl/ca/ca_crl.pem; root /var/tmp; location / { proxy_pass http://puppet-production; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; proxy_set_header X-Client-Verify $ssl_client_verify; proxy_set_header X-SSL-Subject $ssl_client_s_dn; proxy_set_header...

...nfiguration 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 X-Forwarded-For $remote_addr; proxy_connect_timeout 60; proxy_send_timeout 21600; proxy_read_timeout 21600; proxy_pass http://127.0.0.1:8000/stream1; }...

...ing in my template: location <%= location %> { proxy_pass <%= proxy %>; <% if scope.lookupvar(''nginx::resource::location::proxy_header'') then scope.lookupvar(''nginx::resource::location::proxy_header'').each do |header| %> proxy_set_header <%= header %> <% end %> } But i''m getting this error instead: err: Could not retrieve catalog from remote server: Error 400 on SERVER: compile error /etc/puppet/modules/nginx/templates/vhost/vhost_location_proxy.erb:9: syntax error, unexpected $end, expecting kEND ;...

...location @server_error { rewrite ^(.*)$ $scheme://$host permanent; } location @maintenance { rewrite ^(.*)$ $scheme://$host permanent; } sendfile on; send_timeout 300s; location / { proxy_pass http://gancx; proxy_redirect off; proxy_set_header Host $host; proxy_set_header X-Real-IP $remote_addr; proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for; charset UTF-8; client_max_body_size 7m; proxy_buffer_size 4k; proxy_buffers 4 32k;...

...r_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 X-Forwarded-For $remote_addr; proxy_connect_timeout 60; proxy_send_timeout 21600; proxy_read_timeout 21600; proxy_pass http://my_dns_name.tldn:8010; } }...

how does request.host get set? Is there a way to manually set the value in request.host? I have several application servers running rails, each has its own internal address in the request.host, so when calling redirect_to or url_for function, it uses the internal address which is not accessible to the user. what I want is to set request.host to return mysite.com, no matter which application

Hi everybody, I just suscribe to the list because I have a problem using mongrel and mongrel_cluster... I setup a server (debian unstable wich provide apache 2.2.3 as a pakage) but I have an error when I try to access my application : ERROR 403 : Forbidden, You don''t have permission to access / on this server. When I check apache''s logs I found that : [warn] proxy: No

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

Eric, think I came across an issue with the parser in unicorn, with a request (due to 2 layers of nginx proxying) coming across with both a X_FORWARDED_PROTO and a X-Forwarded-Proto header. From the socket (in HttpRequest) - we get: X_FORWARDED_PROTO: http X-Forwarded-Proto: https which is parsed to HTTP_X_FORWARDED_PROTO"=>"http,https There was a passenger ticket that