proxy_pass directive don't catch sequence

located in https://FQDN-Server-Adress:6443/arcgis/login//jsapi/dojo/dojo.js Therefore I've set a proxy_pass directive following the location, but it seems that the involved sequence is not correctly catched up and the malformed url are still returned. What am I doing wrong ? The double slash

Re: Nginx reload intermittenlty fails when protocol specified in proxy_pass directive is specified as HTTPS

und in upstream \"\" > > However, if I changed the protocol mentioned in the proxy_pass directive > from https to http, then the reload goes through. > > Could anyone please explain what mistake I might be doing here? Most likely you are trying to use the same upst

Re: Nginx reload intermittenlty fails when protocol specified in proxy_pass directive is specified as HTTPS

Just one quick question. Does Nginx check if the upstream servers are reachable via the specified protocol, during the reload process? If say, in this case the upstreams are not accepting ssl connections, will the reload fail? Posted at Nginx Forum: https://forum.nginx.org/read.php?2,277399,27741

Re: Nginx reload intermittenlty fails when protocol specified in proxy_pass directive is specified as HTTPS

reload the Nginx configuration, it fails > intermittently with the below error message > > nginx: [emerg] host not found in upstream \"\" > > However, if I changed the protocol mentioned in the proxy_pass directive > from https to http, then the reload goes through.

Nginx reload intermittenlty fails when protocol specified in proxy_pass directive is specified as HTTPS

With this configuration if I try to reload the Nginx configuration, it fails intermittently with the below error message nginx: [emerg] host not found in upstream \"\" However, if I changed the protocol mentioned in the proxy_pass directive from https to http, then the reload goes through.

Nginx reload intermittenlty fails when protocol specified in proxy_pass directive is specified as HTTPS

: weight=1; keepalive 100; } With this configuration if I try to reload the Nginx configuration, it fails intermittently with the below error message nginx: [emerg] host not found in upstream \"\" However, if I changed the protocol mentioned in the proxy_pass

Re: Proxy_pass Directive !!

shahzaib1232 Wrote: --- > rewrite test.com back to test.com. You mentioned the solution > HTTP-EQUIV="REFRESH" . Is that fine to use this method also, could you > tell > me how to use it with origin ip in nginx ? So client will resend the > reques

Re: Proxy_pass Directive !!

>>1.2.3.4 -> request xx.mp4 -> edge 5.6.7.8 (I don't have that file) -> send client address of origin and tell client to re-initiate file request with origin address. @itpp, you're always the light of hope in darkness :-).Thats the exact solution i need, rewrite is not recommended in our solution

Re: Proxy_pass Directive !!

Use a resirect, keep it clean, simple, and compliant Why waste reaources when you dont have to? -- Payam Chychi Network Engineer / Security Specialist On Saturday, July 19, 2014 at 10:47 AM, Anoop Alias wrote: > > > > The Proxying server does not download the entire file ;save it to dis

Re: Proxy_pass Directive !!

The Proxying server does not download the entire file ;save it to disk and then serve from that . The proxy simply buffers the content (which is config manageable) and serve the end user (browser ) .So the proxy will not face a high disk i/o load like the origin .. -- *Anoop P Alias* GNUSYS

Re: Proxy_pass Directive !!

​On Sat, Jul 19, 2014 at 5:57 PM, itpp2012 wrote: > No :) I'd do it simple by using HTTP-EQUIV="REFRESH" as a response with an > origin address. > ​Redirecting that way *might* work, although it looks a bit ugly to my eyes. It also seems to be not compliant to WCAG if you care about accessibilit

Re: Proxy_pass Directive !!

B.R. Wrote: --- > > How? don't ask me :) > > > ​ > Is there a legal problem doing that? Why the smiley? No :) I'd do it simple by using HTTP-EQUIV="REFRESH" as a response with an origin address. Posted at Nginx Forum: http://forum.nginx.org/rea

Re: Proxy_pass Directive !!

On Sat, Jul 19, 2014 at 4:27 PM, itpp2012 wrote: > shahzaib1232 Wrote: > --- > > Means, both server's i/o will be used if the requested file to > > upstream is > > 720p.mp4? > > Yes, what you're looking for is a way to client-rewrite the address

Re: Proxy_pass Directive !!

shahzaib1232 Wrote: --- > Means, both server's i/o will be used if the requested file to > upstream is > 720p.mp4? Yes, what you're looking for is a way to client-rewrite the address the source is coming from. 1.2.3.4 -> request xx.mp4 -> edge 5

Re: Proxy_pass Directive !!

>>If nginx needs to proxy_pass, then before nginx sends content to client, nginx asks upstream for content, and upstream sends content to nginx. So the full file also goes from upstream to nginx. Means, both server's i/o will be used if the requested file to upstream is 720p.mp4? _

Re: Proxy_pass Directive !!

On Sat, Jul 19, 2014 at 02:23:49PM +0500, shahzaib shahzaib wrote: Hi there, > I am confused about the proxy_pass directive. Suppose, i need to serve an > mp4 file from Origin server and using proxy_pass directive in Edge server, > whose resources(I/o,bandwidth,Ram) will be used ? Edge

Proxy_pass Directive !!

I am confused about the proxy_pass directive. Suppose, i need to serve an mp4 file from Origin server and using proxy_pass directive in Edge server, whose resources(I/o,bandwidth,Ram) will be used ? Edge or Origin ? Following is the topology to server mp4 file :- client (request mp4 file

Re: Using Domain Names in proxy_pass directive

This solution would really help . Thanks a lot for the info .. :) Regards Shobhit Mishra Posted at Nginx Forum: http://forum.nginx.org/read.php?2,250307,250341#msg-250341 ___ nginx mailing list nginx@nginx.org http://mailman.nginx.org/mailman/listin

Re: Using Domain Names in proxy_pass directive

On Friday 23 May 2014 08:41:09 Shobhit Mishra wrote: [..] > Does nginx honor TTL for the FQDN in the upstream block as well ?? > > As per my understanding nginx resolves FQDN in upstream blocks only during > configuration parsing .. > > Please suggest on this. Look at the "resolve" parameter: ht

Re: Using Domain Names in proxy_pass directive

Thanks Ruslan for the reply .. I have another query regarding this .. I am planning to use more than one backend servers for supporting Load balancing. I would be using an upstream block for the same. My default configuration is as below : upstream us1 { server sbc.example1.com:443 ; server

Re: Using Domain Names in proxy_pass directive

On Fri, May 23, 2014 at 07:39:36AM -0400, Shobhit Mishra wrote: > Hi > > I am using nginx as reverse proxy with FQDN for the backend server . > > My configuration for the location block looks like this :- > > location / { > > set $ustreamsbc sbc.example.com ; > proxy_pass HTTPS://$ustrea

Using Domain Names in proxy_pass directive

Hi I am using nginx as reverse proxy with FQDN for the backend server . My configuration for the location block looks like this :- location / { set $ustreamsbc sbc.example.com ; proxy_pass HTTPS://$ustreamsbc ; proxy_next_upstream error timeout invalid_header http_500

Re: Error message: invalid number of arguments in "proxy_pass" directive ...

On Tue, May 28, 2013 at 02:35:33PM -0400, ZyntraX wrote: Hi there, > He keeps giving met this error: > [emerg] invalid number of arguments in "proxy_pass" directive in > /etc/nginx/sites-enabled/default.save:35 What is on line 35 of the file /etc/nginx/sites-enabled/default.s

Error message: invalid number of arguments in "proxy_pass" directive ...

Hello guys I'm using nginx as a load balancer between 2 apache webservers for a school assignment, but i can't get it working. My nginx server (running on ubuntu server) won't start... He keeps giving met this error: [emerg] invalid number of arguments in "proxy_pass"