[tor-dev] How to run a headless second Firefox instance?

Ximin Luo infinity0 at torproject.org
Wed Apr 9 15:31:57 UTC 2014

On 09/04/14 07:29, David Fifield wrote:
> It gets the job done, but it sucks because the first thing you see is
> the dialog and you have to know not to close it. Is there a way to
> accomplish the same thing (keep the browser running, but don't show a
> browser window) without raising a conspicuous dialog?

You could play further with this:

$ nc -l -p 9999 &
$ iceweasel -no-remote -p testing -chrome http://localhost:9999

If there's no server listening, firefox opens up a "can't connect" page. Otherwise, it continues running, with no UI, past the 3-minute TCP timeout mark, even if you kill nc in the meantime.

However, I am not sure if the process is actually responsive, or simply hanging waiting for an HTTP response - so you'll need to test that. Also, there's no guarantee that firefox will keep this behaviour.

Failing everything, maybe you could return a real XUL response that displays "don't close me"?



-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 880 bytes
Desc: OpenPGP digital signature
URL: <http://lists.torproject.org/pipermail/tor-dev/attachments/20140409/09c01f70/attachment.sig>

More information about the tor-dev mailing list