Changes between Initial Version and Version 1 of Ticket #3455, comment 64


Ignore:
Timestamp:
Oct 29, 2014, 8:50:18 PM (5 years ago)
Author:
arthuredelstein
Comment:

Legend:

Unmodified
Added
Removed
Modified
  • Ticket #3455, comment 64

    initial v1  
    22> After a quick look at the Torbutton side of the code -- I am wondering what happens with favicons. Historically, Mozilla's filters often miss those.
    33
    4 I made a small test at http://arthuredelstein.github.io/faviconDemo.html, which consists of a tiny html page with a link to a favicon. Annoyingly, the Firefox network tab does not show the favicon.ico request. So I examined the tor-SOCKS conncetion with tcpdump. After clearing the browser cache and browsing to the test, I could see two HTTP GET request/response pairs through the same socket connection, one for faviconDemo.html and one for favicon.ico. So favicon.ico is passing through tor. The first request was preceded by a SOCKS username:password request being set to arthuredelstein.github.io:0. There wasn't a second username:password request.
     4I made a small test at https://arthuredelstein.github.io/tbtests/faviconDemo.html, which consists of a tiny html page with a link to a favicon. Annoyingly, the Firefox network tab does not show the favicon.ico request. So I examined the tor-SOCKS conncetion with tcpdump. After clearing the browser cache and browsing to the test, I could see two HTTP GET request/response pairs through the same socket connection, one for faviconDemo.html and one for favicon.ico. So favicon.ico is passing through tor. The first request was preceded by a SOCKS username:password request being set to arthuredelstein.github.io:0. There wasn't a second username:password request.
    55
    66But at the same time, watching the tor Control Port, I could see only one STREAM event: