Hello!
On Mon, Dec 14, 2015 at 04:26:33PM -0800, Sunil Shah wrote:
> We're running Jenkins behind an Nginx reverse proxy and see issues where
> Jenkins running in Tomcat returns 404 because it receives URLs that have $
> encoded as %24. From the Tomcat logs:
> 10.0.7.212 - - [15/Dec/2015:00:15:22
Hi,
I have an issue where I need to move a site that has a legacy C cgi
interface onto a server that already has FCGI hosts. Rather than trying
to mix slow cgi and fast cgi I was thinking of using fcgiwrap ... does
anyone know if this plays well with a regular fcgi setup on the same
server?
--
N
Hi,
We're running Jenkins behind an Nginx reverse proxy and see issues where
Jenkins running in Tomcat returns 404 because it receives URLs that have $
encoded as %24. From the Tomcat logs:
10.0.7.212 - - [15/Dec/2015:00:15:22 +] "POST
/%24stapler/bound/c43ae9fc-dcca-4fbe-b247-82279fa65d55/ren
My specific use case is to support an HTTP/2 application behind a load
balancer (reverse proxy).
Also as a backend LB between services that could use a long running HTTP/2
connection to do their communication.
Places where I need an LB, but also know that both ends would /prefer/ to
use HTTP/2.
Hello!
On Mon, Dec 14, 2015 at 09:57:02AM -0800, Frank Liu wrote:
> "multiplexing" seems to be a good use case for upstream proxying. We don't
> have control how fast end users adopting HTTP/2, so we may still have tons
> of HTTP/1.x requests coming in, but we can certainly upgrade upstream
> ser
On Monday 14 December 2015 09:57:02 Frank Liu wrote:
> "multiplexing" seems to be a good use case for upstream proxying. We don't
> have control how fast end users adopting HTTP/2, so we may still have tons
> of HTTP/1.x requests coming in, but we can certainly upgrade upstream
> servers that we co
"multiplexing" seems to be a good use case for upstream proxying. We don't
have control how fast end users adopting HTTP/2, so we may still have tons
of HTTP/1.x requests coming in, but we can certainly upgrade upstream
servers that we control to support HTTP/2. If nginx upstream proxy module
can a
Hello!
On Sun, Dec 13, 2015 at 09:28:27PM -0500, winghokwan wrote:
> I have the same issue. I use Lua and Redis for the reverse proxy lookup and
> don't use upstream. How to use keepalive then?
The only way now is to define upstream{} blocks in advance, and
then provide appropriate upstream{} b
Hello!
On Fri, Dec 11, 2015 at 10:03:15PM +, Nicholas Capo wrote:
> Is HTTP/2 proxy support planned for the near future?
Short answer:
No, there are no plans.
Long answer:
There is almost no sense to implement it, as the main HTTP/2
benefit is that it allows multiplexing many requests wi
Hello!
On Sun, Dec 13, 2015 at 01:32:12PM -0800, Adrian D'Atri-Guiran wrote:
> There is a very old post from September, 2011 which says it is not
> supported, I am just wondering if anything has changed since then?
>
> http://mailman.nginx.org/pipermail/nginx/2011-September/028926.html
Using st
I managed to make some changes (I was using another config file,
although "nginx -t" was showing the correct file, witch is very
strange) and I don't get HTTP 503 back.
The config file now looks like this: http://dpaste.com/18J54VV
The problem I have now is that I get
> 500 (Internal Server Error)
11 matches
Mail list logo