Bugzilla – Bug 14835
Connecting to an old server version using a non-default port should show useful error
Last modified: 2011-01-14 00:34:09 UTC
This bug is split from bug 14789. When a Squeezeplay device is instructed to connect to a version of Squeezebox Server which is too old to support the device, it currently shows a message like 'check your network.' Instead, it should show a message like 'this version of the Squeezebox Server does not support this device. Please update to version x.x.x or higher.' The user should then be prompted to select a different server, including MySqueezebox.com.
Dan notes that there are still relatively few users out there with this problem, but that number will increase drastically as Radios reach customers. This should be fixed before the 7.5 release, in his opinion. Felix, are you the right person for this to be assigned? Or would it be Ben or someone else?
I believe that was in place at one stage, but I am not sure who implemented it. Was that you, Tom?
Tom: Why would a too old server even show up in the list? Should we not exclude servers that are not supported?
FWIW: This works ok with 7.4.0 r7790. I get the following message: Update Software <servername> needs to be updated to a newer version of Squeezebox Server.
Felix I also can not repro this. For me I see a "<7.3 server name> needs to be updated to newer version of the SS software". Are we sure the issue isn't only happening on password protected server?
Copying in Michael's comment number 10 from the other bug: ---QUOTE--- This is not behaving as James described in his comment #3. When trying to connect a Baby to a 7.3.x server, the player is telling me "We couldn't connect to serverxyz. Make sure your computer is turned on and connected to wyour local network, and that Squeezebox Server is currently running.". This is wrong. SP should tell the user that it's trying to connect to an incompatible version. This is a SP bug, not SBS. We can't fix old software versions already installed on the user's computer. ---END QUOTE---
However, it seems like this is not easy to reproduce as Michael describes. Since he has probably gone to bed and we are trying to get this software shipped, I'm going to change the target for additional investigation into what cases cause the issue Michael sees. cc'ing Pat as well to double-check my judgment. :) Michael, were you using a wired or wireless setup? Anything else about your use different from normal that might cause you to get a different error?
It's wireless. Maybe it's due to my using a recent 7.5 firmware? 7866 or close to it? Am 19.10.2009 um 20:58 schrieb bugs@bugs.slimdevices.com: > https://bugs-archive.lyrion.org/show_bug.cgi?id=14835 > > > Chris Owens <chris@slimdevices.com> changed: > > What |Removed |Added > --- > --- > ---------------------------------------------------------------------- > CC| | > pat_ransil@logitech.com > AssignedTo|tom@slimdevices.com | > michael@slimdevices.com > Target Milestone|7.4.1 |7.4.x > > > --- Comment #7 from Chris Owens <chris@slimdevices.com> 2009-10-19 > 11:58:42 PDT --- > However, it seems like this is not easy to reproduce as Michael > describes. > Since he has probably gone to bed and we are trying to get this > software > shipped, I'm going to change the target for additional investigation > into what > cases cause the issue Michael sees. > > cc'ing Pat as well to double-check my judgment. :) > > Michael, were you using a wired or wireless setup? Anything else > about your > use different from normal that might cause you to get a different > error? > > -- > Configure bugmail: https://bugs-archive.lyrion.org/userprefs.cgi? > tab=email > ------- You are receiving this mail because: ------- > You are the assignee for the bug.
FWIW: I've also tested with 7.5.0 r7891 and SC 7.3.3 and got the proper message that I need to upgrade SC. There must be something else causing this on your setup, Michael.
Ok, almost all-clear: my 7.3.x instance was using a non-standard port for the web connection (80 instead of 9000). Must have been a left-over from another test. As soon as I switched it back to the default port 9000 I got the correct error message, telling me to update. That's not a deal-breaker any more. But it should still be addressed at some point.
Moving these bugs to P4 to make room for moving P1.5 bugs to P2
Administrative move of 7.5 bugs. All P2, P3, P4 being downgraded one level. Will then split P1s.
Created attachment 6408 [details] SBS should expose version when HTTP auth required SBS currently only exposes its version in SBS 7.4 and 7.5, and for those versions, only AFTER the client has authenticated (see bug 14789). This patch moves the code that adds the SBS version info so that the SBS version info is available BEFORE the client has authenticated, so that Radio owners don't go through the tedium of entering username/password for a too-old server. This patch also changes the format of the text in the Server response header to better match RFC 2616's specifications -- Product/VersionInfo rather than Product (Version Info).
Moving lower-priority bugs to next target