Re: Nginx Location Block

2015-05-26 Thread Julian De Marchi
On 27/05/15 10:15, Francis Daly wrote: > Does the backend configuration include anything that would log to a > different access log, or not log at all? Apparently so... When I access via the frontend my error log for the backend looks like below. Which is quite normal. [haweb-05.vpn] 10:31:58 [er

Re: Nginx Location Block

2015-05-26 Thread Francis Daly
On Wed, May 27, 2015 at 09:58:42AM +1000, Julian De Marchi wrote: > On 27/05/15 09:45, Francis Daly wrote: > > On Mon, May 25, 2015 at 03:44:26PM +1000, Julian De Marchi wrote: Hi there, > >> My issue is when I try to access URIs like /cms/index.php?blah, the > >> frontend Nginx gives 404. Access

Re: Nginx Location Block

2015-05-26 Thread Julian De Marchi
On 27/05/15 09:45, Francis Daly wrote: > On Mon, May 25, 2015 at 03:44:26PM +1000, Julian De Marchi wrote: > > Hi there, > >> Briefly, my setup is using an Nginx frontend server to do SSL offloading >> then pass requests to my backend Nginx servers which then process the >> request via fastCGI. >

Re: Nginx Location Block

2015-05-26 Thread Francis Daly
On Mon, May 25, 2015 at 03:44:26PM +1000, Julian De Marchi wrote: Hi there, > Briefly, my setup is using an Nginx frontend server to do SSL offloading > then pass requests to my backend Nginx servers which then process the > request via fastCGI. > > My issue is when I try to access URIs like /cm

Re: Nginx and Websphere

2015-05-26 Thread Francis Daly
On Tue, May 26, 2015 at 06:36:35AM -0400, sampy wrote: Hi there, > NGINX balancing over 2 servers using ip_hash. This servers runs Websphere > and in every Websphere runs several apps. > > Servers separately runs: > > wasint-1.domain.com:9080/WebApp > wasint-2 domain.com:9080/WebApp > > My con

Re: DNS configuration to invoke complete URL

2015-05-26 Thread Francis Daly
On Tue, May 26, 2015 at 10:20:27AM -0400, smsmaddy1981 wrote: Hi there, >server { >listen 80; >server_name workspace.corp.no; > >location / { > proxy_pass http://workspace.corp.no/workspace/agentLogin; >} > } > > Expected to see: > accessing URL

Re: host names in 1.9

2015-05-26 Thread Francis Daly
On Tue, May 26, 2015 at 06:47:19PM -0400, sentinel21 wrote: Hi there, > I'm having some difficulty using the stream directive in 1.9. I may be > using it wrong, so please correct me if this is incorrect or not possible. A connection comes to an ip:port. A http connection includes a specific h

host names in 1.9

2015-05-26 Thread sentinel21
I'm having some difficulty using the stream directive in 1.9. I may be using it wrong, so please correct me if this is incorrect or not possible. stream { server { listen 1520; server_name customhost.example.com proxy_pass db; } upstream db { server 1

Measuring request processing time

2015-05-26 Thread Дмитрий Шалашов
Hi! Is there a way to measure time Nginx takes to process request? Not $request_time, but rather something like "time between request was fully read and request is ready to pass it to the backend". I need it to evaluate perfomance of the geoip2 module: https://github.com/leev/ngx_http_geoip2_modul

Re: nginx on Debian: dynamic network interfaces

2015-05-26 Thread Maxim Dounin
Hello! On Tue, May 26, 2015 at 05:53:00PM +0200, B.R. wrote: > Hello, > > Facing issues on Debian with official nginx packages, I filled a bug up on > the Debian tracker which ended up as being closed since Debian refers to > the faulty service(s), nginx being one. > > ​Bug #785253

nginx on Debian: dynamic network interfaces

2015-05-26 Thread B.R.
Hello, Facing issues on Debian with official nginx packages, I filled a bug up on the Debian tracker which ended up as being closed since Debian refers to the faulty service(s), nginx being one. ​Bug #785253 ​ ​I could not fill a bug on h

Re: DNS configuration to invoke complete URL

2015-05-26 Thread smsmaddy1981
Thanks for the response #Vikrant and #Valentin Below are the issue details: What I have Configured: server { listen 80; server_name workspace.corp.no; location / { proxy_pass http://workspace.corp.no/workspace/agentLogin; } } Expected to see: access

nginx-1.9.1

2015-05-26 Thread Maxim Dounin
Changes with nginx 1.9.1 26 May 2015 *) Change: now SSLv3 protocol is disabled by default. *) Change: some long deprecated directives are not supported anymore. *) Feature: the "reuseport" parameter of the "listen" directive. Thanks to S

Nginx and Websphere

2015-05-26 Thread sampy
Hi all! I'm new in NGINX but I have try everything with very bad results. My scenario is: NGINX balancing over 2 servers using ip_hash. This servers runs Websphere and in every Websphere runs several apps. Servers separately runs: wasint-1.domain.com:9080/WebApp wasint-2 domain.com:9080/WebApp