Comment 14 for bug 1244629

It's nice to see it's patched for the immediate problem and will probably eventually make it into the Precise updates. What I did to see what was happening was to use Wireshark. It was getting a 301 response (or was that 302?). Wouldn't it be nicer if the plugin properly followed redirects such as this? I was looking in weather-http.c, but I wasn't too sure about the BEST place to parse the response code and the Location: header. I also wasn't too sure of how to handle a 301, such as changing the appearance somehow, because it could go from working, to 301, to 404, and developers wouldn't otherwise see it until it totally breaks at the 404 stage (or in this case, at some other time if xoap is removed from DNS).