RE: Invalid character found in the request target on Confluence behind nginx

2018-12-11 Thread Dung Tran Tien
ecember 11, 2018 3:59 PM To: nginx@nginx.org Subject: Re: Invalid character found in the request target on Confluence behind nginx On Tue, Dec 11, 2018 at 08:54:23AM +, Dung Tran Tien wrote: Hi there, > Not sure I understand you correctly. If change as suggest like > > l

Re: Invalid character found in the request target on Confluence behind nginx

2018-12-11 Thread Francis Daly
On Tue, Dec 11, 2018 at 08:54:23AM +, Dung Tran Tien wrote: Hi there, > Not sure I understand you correctly. If change as suggest like > > location /confluence { > > proxy_pass http://1.1.2.1:8090/; Ah, there's the problem. That's not what I suggested. You have one "/" in your c

RE: Invalid character found in the request target on Confluence behind nginx

2018-12-11 Thread Dung Tran Tien
x.org Subject: Re: Invalid character found in the request target on Confluence behind nginx On Tue, Dec 11, 2018 at 08:39:32AM +, Dung Tran Tien wrote: Hi there, > The backend must have context /confluence, without it, the page cannot be > load with 404 code. Yes. The reque

Re: Invalid character found in the request target on Confluence behind nginx

2018-12-11 Thread Francis Daly
On Tue, Dec 11, 2018 at 08:39:32AM +, 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.

RE: Invalid character found in the request target on Confluence behind nginx

2018-12-11 Thread Dung Tran Tien
Hi, The backend must have context /confluence, without it, the page cannot be load with 404 code. -Original Message- From: nginx On Behalf Of Francis Daly Sent: Tuesday, December 11, 2018 3:35 PM To: nginx@nginx.org Subject: Re: Invalid character found in the request target on

Re: Invalid character found in the request target on Confluence behind nginx

2018-12-11 Thread Francis Daly
On Tue, Dec 11, 2018 at 03:15:52AM +, Dung Tran Tien wrote: Hi there, In this case, I think that there is a straightforward change that can work: >location /confluence { > proxy_pass http://1.1.2.1:8090/confluence; Change that line to just be proxy_pass http://1.1.2.1:8090;

RE: Invalid character found in the request target on Confluence behind nginx

2018-12-10 Thread Dung Tran Tien
Original Message- From: nginx On Behalf Of Francis Daly Sent: Tuesday, December 11, 2018 6:10 AM To: nginx@nginx.org Subject: Re: Invalid character found in the request target on Confluence behind nginx On Mon, Dec 10, 2018 at 06:43:13AM +, Dung Tran Tien wrote: Hi there, &

Re: Invalid character found in the request target on Confluence behind nginx

2018-12-10 Thread Francis Daly
On Mon, Dec 10, 2018 at 06:43:13AM +, Dung Tran Tien wrote: Hi there, > Currently I'm using Confluene 6.10.2 behind nginx. I have some pages with the > page name including character '>' could not accessible, the error is: > But when I access the page bypassing the reverse proxy, it's ok, so

Invalid character found in the request target on Confluence behind nginx

2018-12-09 Thread Dung Tran Tien
Hi, Currently I'm using Confluene 6.10.2 behind nginx. I have some pages with the page name including character '>' could not accessible, the error is: HTTP Status 400 - Bad Request Type Exception Report Message Invalid character found in the request target. The valid characters are defined in R