that’s everyday with the legacy web app at work, it crunches up code in a templating process and all the errors become either completely meaningless or just “error 500”
that’s IIS as well, I think it’s because we had our severs configured in a reverse proxy and hitting IIS and failing before the http serverhad returned a response caused the 502 error, completely useless error.
(not very experienced with server configs so forgive me if the language isn’t 100%)
that’s everyday with the legacy web app at work, it crunches up code in a templating process and all the errors become either completely meaningless or just “error 500”
Reminds me of AWS Lambda. Gateway Error 502 you say? Gotta go digging in the application logs!
that’s IIS as well, I think it’s because we had our severs configured in a reverse proxy and hitting IIS and failing before the http serverhad returned a response caused the 502 error, completely useless error.
(not very experienced with server configs so forgive me if the language isn’t 100%)