I just observed this bug as well after upgrading xul-ext-firebug from 1.5.4-2 to 1.7~b1-1 (iceweasel is 3.5.17-1).
After receiving a 302, Iceweasel issues a request for the location in the 302 (observed in Wireshark), but never renders the result. This behavior was observed on all pages returning 302 (comically http://bugs.debian.org/xul-ext-firefox as well... which made finding this bug more interesting). However, after disabling the add-on, restarting, and re-enabling it, the behavior appears to have ceased. Perhaps someone experiencing this bug in the future can help get to the root cause before the disable/re-enable step... -- Cheers, | ke...@kevinlocke.name | JIM: kevin...@jabber.org Kevin | http://kevinlocke.name | IRC: kevinoid on freenode -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
