Persistance of 504 error in browser (Chrome)

by user225067   Last Updated August 13, 2019 18:03 PM

We were recently trying to migrate our app behind an AWS elastic load balancer (ELB). Due to some configuration issues, the ELB started genrating 504 Gateway Timeout error on the browser.

As a result, we decided to remove ELB and go back to our original configuration. Essentially we changed our DNS A records. However, browser (Chrome in this case) continue to give use 504 error. We could visit our app in incognito mode or using another browser which had not seen 504 error.

The only solution was to clear browser cache/cookies (clearing cache alone did not work). After performing this step, everything was fine.

I am still perplexed by this issue. How is browser not able to redirect after DNS record changes? what has cookie got to do with this?

Related Questions

Updated August 24, 2017 16:03 PM

Updated September 18, 2017 17:03 PM

Updated August 11, 2015 17:01 PM

Updated September 02, 2017 08:03 AM

Updated March 30, 2018 07:03 AM