Indeed. I just found that edge.launchpad.net is routing/presenting some HTTP requests to/as https://edge.lp.net, instead of the stable https://bugs.edge.lp.net. As a result, the GM scripts fail on a XSS (since we are running off https://bugs.edge.lp.net, and the request is sent over to https://edge.lp.net).
I have not looked at tamperdata output, but firebug shows a 200 status, while the event handler in JS shows a status == 0.
Going back to https://bugs.launchpad.net makes the scripts work. So. Something changed on Edge.
Can someone please confirm the above?
Indeed. I just found that edge.launchpad.net is routing/presenting some HTTP requests to/as https:/ /edge.lp. net, instead of the stable https:/ /bugs.edge. lp.net. As a result, the GM scripts fail on a XSS (since we are running off https:/ /bugs.edge. lp.net, and the request is sent over to https:/ /edge.lp. net).
I have not looked at tamperdata output, but firebug shows a 200 status, while the event handler in JS shows a status == 0.
Going back to https:/ /bugs.launchpad .net makes the scripts work. So. Something changed on Edge.
Can someone please confirm the above?