One thing that creeped up was the recent firefox update to 220.127.116.11. I was starting to wonder if that was the culprit. So decided to check on it. Fortunately, I had another machine that was running 18.104.22.168. I was unable to access the development server URL from the other machine(which should be the case), So I went to IIS, setup a website, pointing it to the same directory as the development server. Then I accessed the website on Firefox 22.214.171.124 and found that everything was fine. But hold on a sec, What if the problem is with the asp.net development server and not with the latest release of Firefox?
I went back to Firefox 126.96.36.199 and fired the website from IIS and bingo everything was working as usual. So it definitely is a problem with the development server. Another problem solved 🙂