Invalid character found in the request target on Confluence behind nginx

Tue Dec 11 08:54:23 UTC 2018

Hi there,

Not sure I understand you correctly. If change as suggest like

location /confluence {

         proxy_pass http://1.1.2.1:8090/;

The request from the client is for /confluence/something.

The request from nginx to backend is for /something, it's not correct.

Besides that, my current configuration from this guide https://confluence.atlassian.com/confkb/how-to-use-nginx-to-proxy-requests-for-confluence-313459790.html.

Your sincerely,
Dung

-----Original Message-----
From: nginx <nginx-bounces at nginx.org> On Behalf Of Francis Daly
Sent: Tuesday, December 11, 2018 3:43 PM
To: nginx at nginx.org
Subject: Re: Invalid character found in the request target on Confluence behind nginx

On Tue, Dec 11, 2018 at 08:39:32AM +0000, Dung Tran Tien wrote:

Hi there,

> The backend must have context /confluence, without it, the page cannot be load with 404 code.

Yes.

The request from the client is for /confluence/something.

The request from nginx is for /confluence/something.

              f

--

Francis Daly        francis at daoine.org<mailto:francis at daoine.org>

_______________________________________________

nginx mailing list

nginx at nginx.org<mailto:nginx at nginx.org>

http://mailman.nginx.org/mailman/listinfo/nginx
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.nginx.org/pipermail/nginx/attachments/20181211/04d173c9/attachment.html>