Comment 2 for bug 1180599

I've since updated to the latest revisions and the problem has now gone away. Hopefully it was just a side-effect of some small server change, or something I just had wrong? Either way, I can't reproduce it on my own any more, so I guess it's resolved.

Thanks for looking into it!