Uzbl

Tasklist

FS#272 - "Connection Terminated Unexpectedly" when trying to access Facebook.com

Attached to Project: Uzbl
Opened by Dennis Hodapp (thehodapp) - 2011-06-12 01:04:59 AM
Task Type Bug Report
Category uzbl-browser & sample material
Status Unconfirmed
Assigned To No-one
Operating System Linux
Severity Medium
Priority Normal
Reported Version Development
Due in Version Undecided
Due Date Undecided
Percent Complete 0%
Votes 0
Private No

Details

Using multiple versions of Uzbl on different Linux OS's, I've come across this problem. What happens is I am able to log into Facebook just fine (say after a fresh install of Uzbl with cleaned out cookies). I'm able to browse the site just fine. Logging out and in does not cause problems. Usually after a few times of exiting and restarting Uzbl, then the bug happens, when I try to visit facebook.com, http://facebook.com, https://facebook.com or basically any incarnation I can think of for the URL, I get the Uzbl "Unable to Load Page" and below, "Connection Terminated Unexpectedly". The only fix I've been able to find is to delete all of the Facebook cookies which afterward allows connection to Facebook.

Here is the output from uzbl-browser -v after the problem has occured (cookies omitted for security reasons. Devs can contact me if they would like their output):

Navigation requested -> https://google.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'https://google.com/' -- result: true
Stdout:
Uzbl start location: uzbl-core
window_id 33554463
pid 13548
name: 33554463
commit: 2011.04.12-133-g79270bf
Navigation requested -> http://www.google.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'http://www.google.com/' -- result: true
Stdout:
Navigation requested -> about:blank
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'about:blank' -- result: true
Stdout:
External JavaScript file /home/dennis/.local/share/uzbl:/usr/share/uzbl/examples/data:scripts/formfiller.js loaded
External JavaScript file /home/dennis/.local/share/uzbl:/usr/share/uzbl/examples/data:scripts/follow.js loaded
spawned: '/usr/share/uzbl/examples/data/scripts/history.sh' -- result: true
Navigation requested -> http://facebook.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'http://facebook.com/' -- result: true
Stdout:
Navigation requested -> http://facebook.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'http://facebook.com/' -- result: true
Stdout:
Navigation requested -> https://google.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'https://google.com/' -- result: true
Stdout:
Uzbl start location: uzbl-core
window_id 33554463
pid 13548
name: 33554463
commit: 2011.04.12-133-g79270bf
Navigation requested -> http://www.google.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'http://www.google.com/' -- result: true
Stdout:
Navigation requested -> about:blank
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'about:blank' -- result: true
Stdout:
External JavaScript file /home/dennis/.local/share/uzbl:/usr/share/uzbl/examples/data:scripts/formfiller.js loaded
External JavaScript file /home/dennis/.local/share/uzbl:/usr/share/uzbl/examples/data:scripts/follow.js loaded
spawned: '/usr/share/uzbl/examples/data/scripts/history.sh' -- result: true
Navigation requested -> http://facebook.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'http://facebook.com/' -- result: true
Stdout:
Navigation requested -> http://facebook.com/
spawned: '/usr/share/uzbl/examples/data/scripts/scheme.py' 'http://facebook.com/' -- result: true
Stdout:
This task depends upon

Comment by Brendan Taylor (bct) - 2011-07-05 12:24:38 AM
I had a similar issue with this, I suspect it has something to do with the massive number of cookies that Facebook stores for some reason. My solution was to only whitelist the cookies you actually need to log in:

request WHITELIST_COOKIE domain '^(.*\.|)facebook\.com$' name '^(c_user|datr|lu|sct|sid|xs)$'
request WHITELIST_COOKIE domain '^(.*\.|)fbcdn\.net$'

Using a whitelist will automatically blacklist everything else though, so to do this with a targetted blacklist use something like this:

request BLACKLIST_COOKIE domain '^(.*\.|)facebook\.com$' name '^(?!(c_user|datr|lu|sct|sid|xs))$'

That has not been tested.

Also before this will work you need to delete the cookies that facebook already saved, "grep -v facebook cookies.txt" should do that for you.

Loading...