Re: HTTP/2 Gateway

2015-12-11 Thread Nicholas Capo
Is HTTP/2 proxy support planned for the near future? Nicholas On Sun, Dec 6, 2015 at 8:14 PM Maxim Dounin wrote: > Hello! > > On Sun, Dec 06, 2015 at 03:00:23PM +0100, bjun...@gmail.com wrote: > > > i've tried to use nginx as http/2 gateway for backends which only > > supporting HTTP 1.1. If

Re: How to set up nginx for file uploading

2015-12-11 Thread Richard Stanway
"The response had HTTP status code 503. " It looks your backend is failing, as it's returning a HTTP/503 error and likely not including the correct headers. You should look into why your backed is returning a 503 as this doesn't seem like an nginx issue any more. On Fri, Dec 11, 2015 at 3:50 PM,

Re: How to set up nginx for file uploading

2015-12-11 Thread Vlad Fulgeanu
I added these in "location /upload/preview": add_header 'Access-Control-Allow-Origin' 'https://test.project.com'; > add_header 'Access-Control-Allow-Headers' 'Authorization, Content-Type, > X-Requested-With, Cache-Control, If-None-Match'; And now it gives me: No 'Access-Control-Allow-Origin' he

Re: How to set up nginx for file uploading

2015-12-11 Thread Richard Stanway
Your config doesn't appear to add any Access-Control-Allow-Origin header, so unless your backend is adding this, you will need to add an appropriate Access-Control-Allow-Origin header. On Fri, Dec 11, 2015 at 1:14 PM, Vlad Fulgeanu wrote: > Hi everyone! > > I am having some trouble setting up ng

How to set up nginx for file uploading

2015-12-11 Thread Vlad Fulgeanu
Hi everyone! I am having some trouble setting up nginx for file uploading. I am using nginx as a proxy in front of my nodejs server (that has hapi as server framework). Here is the nginx.conf file's portion for this server: http://dpaste.com/0VJKE5K The problem is that I get > No 'Access-Contr

Re: Next upstream based on custom http code

2015-12-11 Thread Frank Liu
Here is my flow: client - nginx - upstream - real upstream Upstream is getting the response from the 'real' upstream. So if real upstream is wrong, nginx will get standard 5xx from upstream and in this case I don't really want nginx to try next upstream because it will hit the same bad real upstre

Re: Next upstream based on custom http code

2015-12-11 Thread B.R.
If the upstream refuses to process a request, you might wish to emulate an unavailable service or a lack of response (timeout). Backend up and working are expected to process requests. Switching between legitimate errors and faked one will be done by monitoring backend logs. There is no such thing