An error occurred in our ASP.NET application, where a URL on an anchor was wrong.
Production workers did an emergency repair by rewriting the URL of the page on the Big-IP F5 hardware load balancer.
Now we have to fix the bug, but I can not see it in code. Everything looks correct. We can not recreate the error, even in QA. The only way to regenerate seems to be to return the F5 configuration which will break a working system.
What to do?
Can not you bypass F5 for debugging purposes? Browse the IP address of the actual webserver rather than loaded IP?
Comments
Post a Comment