My current setup uses a vert.x server running behind Nginx setup as a reverse proxy. 499 responses are issued by Nginx when the client closes the connection (i.e. connection timeout).
I recently noticed Nginx produced a 499 response after a client sent a POST request to my server (I'm guessing this client had a poor internet connection, the request was made on a mobile device). Every subsequent POST request resulted in a 499 response. I was debugging the issue and concluded my Nginx setup was fine and the issue was related to my vertx code. I was suspecting this was the result of not implementing the failureHandler method on my post route or it may have been another issue in my code. I've looked deeper into the documentation and have added the failureHandler into my handler code.
Is this the right way to prevent Nginx from producing 499 responses in the future? What would cause the vertx server to do something like this?
--
You received this message because you are subscribed to the Google Groups "vert.x" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
vertx+un...@googlegroups.com.
Visit this group at
https://groups.google.com/group/vertx.
To view this discussion on the web, visit
https://groups.google.com/d/msgid/vertx/86b956e2-f758-47dc-8eab-b16c6f3d960d%40googlegroups.com.
For more options, visit
https://groups.google.com/d/optout.