Show all posts by user
A portal to and from the mailing list.
Re: ipV6 failing first time, working everytime subsequently - 1 year ago
Hello Francis, 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 Coby chakras - Nginx Mailing List - English
Re: ipV6 failing first time, working everytime subsequently - 1 year ago
Hello Francis, Thanks for your response. I have verified from Network logs on the browser that POST request is sending the username and password in both cases. So, I wasn't sure if additional headers need to be sent for switching to happen seamlessly. The issue is after that first failure there is no subsequent failure for entire session of the application. I am still trying to debug what caby chakras - Nginx Mailing List - English
ipV6 failing first time, working everytime subsequently - 1 year ago
Hello, I am using nginx on a VPS to proxy requests to a GCP server. When working with IPv4, everything works as desired. However, if we enable IPv6 on client machine, we see that the first call (/auth) fails with 401, and all subsequent calls are successful. We cannot see the first call on GCP. I have made sure that AAAA records do exist, GCP endpoint supports IPv6. This is my configuration forby chakras - Nginx Mailing List - English
 |
 |
 |
 |
|