On Sun, Nov 08, 2020 at 09:51:36AM -0500, garyc...@yahoo.com wrote:
Hi there,
> Interestingly, the copy/paste method yields an initial 302 response opposed
> to a 200 response with the click link method.
You have two requests to the same url, getting different responses.
Does your nginx config
On Sun, Nov 08, 2020 at 08:07:07AM -0500, garyc...@yahoo.com wrote:
Hi there,
> Nginx is configured as a reverse proxy server in this architecture. It is
> successfully working except with this AJAX call.
In general, nginx does not care whether a request to it comes from AJAX,
or clicking a lin
hello team,
i have found that https://hg.nginx.org/nginx-quic (current as of 06 Nov 2020)
is having some trouble properly POSTing back to PayPal using php 7.3.24 on
a Debian Buster box. things work as expected using current mainline nginx
or current quiche. i have verified that PageSpeed is not c
All:
I've made some more progress in that when I copy/paste the AJAX URL into my
browser's address-bar, the MP3 download request is successfully made and the
MP3 is downloaded (opposed to the previous examples when I clicked on the
MP3 download link).
Interestingly, the copy/paste method yields a
Fancis,
Nginx is configured as a reverse proxy server in this architecture. It is
successfully working except with this AJAX call.
Client:54454 ==> NginxMaster:80 | NginxWorker:52312 ==> UpstreamServer:443
UpstreamServer:443 ==> NginxWorker:52312 | NginxMaster:80 ==> Client:54454
The requests
On Sun, Nov 08, 2020 at 10:45:05AM +, Francis Daly wrote:
> On Sun, Nov 08, 2020 at 03:42:05AM -0500, garyc...@yahoo.com wrote:
Actually...
> > GET http://example.com/ajax/inc/1488440 HTTP/1.1
>
> That's a http request...
That's a http request to a http proxy server, not to a http server.
On Sun, Nov 08, 2020 at 03:42:05AM -0500, garyc...@yahoo.com wrote:
Hi there,
> I discovered that the failing request is making a subsequent, asynchronous
> AJAX call to port 443 of Nginx where the connection is failing with
> "Certificate Unknown" against my self-signed certificate.
I'm not qui
All:
I discovered that the failing request is making a subsequent, asynchronous
AJAX call to port 443 of Nginx where the connection is failing with
"Certificate Unknown" against my self-signed certificate.
GET http://example.com/ajax/inc/1488440 HTTP/1.1
Host: example.com
Connection: keep-alive
A
