For some reasons, I just realized that when you click on a rhaplink in Firefox, it spawns Rhapsody on the Web instead of the Rhapsody 3.1 application. It works fine in IE. So I just launched my new favorite tool ethereal to see what was going on.
Apparently, it’s a cookie problem. Firefox doesn’t send all the cookies it’s supposed to (like the rhapsodyinstalled=versionXXX that the JSP looks for to figure out if Rhapsody application is installed on the PC and to decide wether to use Rhapsody on the web or redirect to a true rhap:// rhaplink to spawn the PC app).

That’s amazing this hasn’t been found in QA … I wonder if all the QA guys have left by now…