ss to XMLHttpRequest at 'https://
abc.com/api/21/job/8c1c66b9-a736-4d28-9868-c3f2c433b0f7/executions' from origin
'https://bcd.com' has been blocked by CORS policy: No
'Access-Control-Allow-Origin' header is present on the requested resource.
Please advise me how to fix the
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 +0000, Dung Tran Tien wrote:
Hi there,
> Not sure I understand you correctly. If change as suggest like
>
> l
x.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 reque
Confluence behind
nginx
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
prox
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,
&
s page has been drop by nginx, no record found out in backend
log, please advise me how to fix the issue.
I tried with some solutions, like ignore_invalid_headers to off in http level,
also set rewrite , but no luck
if ($request_uri ~ ^(/.*)[>](.*)$) {
return 301 $1%3E$2;
}
Dung Tra
