On Fri, Jan 07, 2022 at 12:02:03PM -0500, chakras wrote:

Hi there,

> To answer your question partially, username/ password validation happens on
> GCP server. We do a POST request and send a JSON object with those values
> filled in. If the login succeeds, we send back a token. Nginx is really
> working just as a proxy here. Something like this on browser Network debug
> log,
>
> Request URL: https://xxxxx.us/gcp/users/auth
> Request Method: POST
> Status Code: 401
> Remote Address: xxx.xxx.xxx.xxx
> Referrer Policy: strict-origin-when-cross-origin
>
> In this case 401 is valid (I am on IPv4) as the user/ pass was wrong.

I think you have said:

* the initial 401 response comes from GCP
* this initial request does not go to GCP

I don't think that both of those can be correct simultaneously.

Possibly the nginx logs, the GCP logs, or a tcpdump in the middle,
can show what actually happens in this initial request?

That might help you see where things go wrong.

Good luck with it,

f
--
Francis Daly francis@daoine.org
_______________________________________________
nginx mailing list
nginx@nginx.org
http://mailman.nginx.org/mailman/listinfo/nginx