<b>@gimmic</b> I've confirmed that it's definitely the browser that is filtering it... however it doesn't look like the Greasemonkey team is going to make any effort to implement the fix anytime in the near future. Only suggestion for now is to use the DOM XMLHttpRequest in an unsafeWindow over the Greasemonkey API implementation or some combination of both to achieve what you need. <p><b>@gimmic</b></p> <p>I've confirmed that it's definitely the browser that is filtering it... however it doesn't look like the Greasemonkey team is going to make any effort to implement the fix anytime in the near future. Only suggestion for now is to use the DOM XMLHttpRequest in an unsafeWindow over the Greasemonkey API implementation or some combination of both to achieve what you need.</p> 2008-01-02T02:53:35Z 1 Forum 5788 1302 2008-01-02T02:53:35Z 37004