Opened 6 years ago

Closed 2 years ago

#10165 closed defect (wontfix)

Torbrowser surf localhost through Tor

Reported by: toldmikl Owned by: tbb-team
Priority: Medium Milestone:
Component: Applications/Tor Browser Version:
Severity: Normal Keywords: tbb-torbutton
Cc: brade, mcs Actual Points:
Parent ID: Points:
Reviewer: Sponsor:

Description

Hi!

I have a big problem. Yesterday I installed a program called xampp. I typed in the address bar of the TOR browser https://127.0.0.1 and it's working. However, I would need the localhost is reached, but this does not work. Why? Someone can help me?

Child Tickets

Attachments (1)

tor.PNG (92.6 KB) - added by toldmikl 6 years ago.

Download all attachments as: .zip

Change History (11)

Changed 6 years ago by toldmikl

Attachment: tor.PNG added

comment:1 Changed 6 years ago by toldmikl

I attach the picture so you can see what I want to do. I want to open this file: localhost/index.html. How can I do it?

comment:2 Changed 6 years ago by cypherpunks

Support of localhost was destroyed by MiCthulhu because code wasn't maintained.
Need to code some another support, or to fix Firefox bug and then possible to put localhost back to network.proxy.no_proxies_on.

comment:3 Changed 6 years ago by cypherpunks

Priority: criticalnormal
Type: taskdefect

comment:4 Changed 6 years ago by cypherpunks

Summary: I can't use xampp localhost in TOR BrowserTorbrowser surf localhost through Tor

comment:5 Changed 5 years ago by erinn

Component: TorBrowserButtonTor Browser
Keywords: tbb-torbutton added
Owner: changed from mikeperry to tbb-team

comment:6 in reply to:  2 Changed 3 years ago by bugzilla

Milestone: TorBrowserBundle 2.3.x-stable
Severity: Normal

Replying to cypherpunks:

Support of localhost was destroyed by MiCthulhu because code wasn't maintained.

"Support" (a DNS hole) was destroyed when Firefox started to obey Remote DNS rule. Tor refuses to resolve "localhost". So, even if you add "localhost" to network.proxy.no_proxies_on, you get "Unable to find the proxy server" webpage.

Need to code some another support, or to fix Firefox bug

Fixed.

and then possible to put localhost back to network.proxy.no_proxies_on.

If you put something there, you get:

Torbutton INFO: aProxy is null
TypeError: originalProxy is null domain-isolator.js:77:7

Should Tor Browser allow it?

p.s.

I typed in the address bar of the TOR browser ​https://127.0.0.1 and it's working.

Bug. Fixed. In TBB 6.5a2:

[08-21 17:26:30] Torbutton INFO: tor SOCKS: https://127.0.0.1/ via 127.0.0.1:2f492e7768755f3b659f4dcb9c781b59
[08-21 17:26:30] Torbutton INFO: controlPort >> 650 STREAM 7623 NEW 0 127.0.0.1:443 SOURCE_ADDR=127.0.0.1:60727 PURPOSE=USER
[08-21 17:26:30] Torbutton INFO: controlPort >> 650 STREAM 7623 FAILED 0 127.0.0.1:443 REASON=PRIVATE_ADDR
[08-21 17:26:30] Torbutton INFO: controlPort >> 650 STREAM 7623 CLOSED 0 127.0.0.1:443 REASON=PRIVATE_ADDR
[08-21 17:26:30] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
Tor WARN: Rejecting SOCKS request for anonymous connection to private address [scrubbed].

But if you add "127.0.0.1" to network.proxy.no_proxies_on, firefox.exe starts to connect to your xampp.

comment:7 Changed 3 years ago by mcs

Cc: brade mcs added

comment:8 Changed 2 years ago by cypherpunks

I opened online banking site only and saw

[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:17] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:18] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:8080
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5938
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5939
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:3389
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:443
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5900
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5931
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:80
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5650
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:51
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:5985
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:6900
[05-31 15:46:20] TorLauncher NOTE: WARN DANGEROUS_SOCKS PROTOCOL=SOCKS5 ADDRESS=127.0.0.1:445

I found only this ticket by searching "TorLauncher NOTE: WARN DANGEROUS_SOCKS", so I pasted it here.
What do all that mean? Is that site trying to attack my computer, or how can I interpret that?
Thanks in advance.

comment:9 Changed 2 years ago by arma

For the original ticket: you are never going to be able to surf to localhost via Tor Browser, because that would open up too many proxy bypass holes.

For the new comment: neat bug! I have opened #22461 to track it. It's harmless -- just a scary warning if you happen to be listening to the warnings.

comment:10 Changed 2 years ago by arma

Resolution: wontfix
Status: newclosed

Closing original bug as wontfix, because localhost isn't something you should usefully go to with Tor Browser.

Note: See TracTickets for help on using tickets.