#25321 closed defect (fixed)

Unable to comment on independent.co.uk

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

Description

Until a week or two ago (I don't comment every day, so it might have been a month ago) I was able to comment on the independent.co.uk news site. Now I cannot comment with Tor (I don't want anyone to know who is making my comments).

Am I doing something wrong? Before, I wrote in, and the problem was that comments were insecure, while the news articles were https secure, and I learned how to disable that protection. Now I cannot log in at all.

I have no idea if the Independent is blocking all comments from Tor users as part of its firewall, or if Tor has some protection against the kind of stuff they try to extract from commentators.

Any help or advice would be appreciated.

Child Tickets

Attachments (3)

errorswhentryingtocomment.doc (507.5 KB) - added by mwolfe 21 months ago.
jslogindependent.txt (4.7 KB) - added by mwolfe 21 months ago.
browser console js
browserlogindependent.txt (5.1 KB) - added by mwolfe 21 months ago.

Download all attachments as: .zip

Change History (12)

comment:1 Changed 21 months ago by cypherpunks

Component: - Select a componentApplications/Tor Browser
Owner: set to tbb-team

comment:2 Changed 21 months ago by cypherpunks

Status: newneeds_information

I wanted to test this but the site is bloated like no tomorrow xD

What I can suggest you to try to diagnose the issue:

  1. Open the Browser Console using Ctrl+Shift+J and see if any error pops up when you try to comment.
  2. Click on the HTTPS Everywhere icon and select "Block all unencrypted requests", then refresh the page where you want to comment and see if it's fixing thing.

comment:3 Changed 21 months ago by Jaruga

If you can't log in at all without any formal notice (i.e. No "We no longer allow Tor connections" notifier, simply a reloaded blank login form, etc) I would imagine that it has to do with either your cookies or referrer settings. Have you tweaked the internals in about:config? How are you configuring NoScript?

Changed 21 months ago by mwolfe

comment:4 Changed 21 months ago by mwolfe

  1. I tried Ctrl+Shift+J and saved all the errors (attached)
  2. I clicked on the HTTPS Everywhere button, but did not see "Block all unencrypted requests"

I tried playing with HTTPS options. No help. So I reset everything in the Options menu back to default (I hope). I haven't done anything (that I can recall) with about:config

comment:5 in reply to:  4 Changed 21 months ago by cypherpunks

Replying to mwolfe:

  1. I tried Ctrl+Shift+J and saved all the errors (attached)

Wow, that's 126 pages, and we only wanted the part when you tried to comment (i.e. 5 lines at most) :)

Also why .doc when you could've just saved it as a .txt that our browsers can parse, were it not for https://drive.google.com/viewer?url=https://trac.torproject.org/projects/tor/raw-attachment/ticket/25321/errorswhentryingtocomment.doc I wouldn't been able to read it :)

Anyway, I assume the last parts are those that are related to your browsing on the independent, anyway I see that there are some errors like

TypeError: can't access dead object webbrowser.js:2508:1
Object { readyState: 0, getResponseHeader: .ajax/v.getResponseHeader(a),
getAllResponseHeaders: .ajax/v.getAllResponseHeaders(), setRequestHeader:
.ajax/v.setRequestHeader(a, b), overrideMimeType: .ajax/v.overrideMimeType(a),
statusCode: .ajax/v.statusCode(a), abort: .ajax/v.abort(a), state: .Deferred/d.state(),
always: .Deferred/d.always(), then: .Deferred/d.then(), 10 more… } js__12ka-
7VVKLLsnpn89DAEyT6Ny99XhemGe4MO3RK2ldI__LZnVzy1JPDXxDPQKZmRb9
DFFjBobAUrHWcLUaHkXS_Q__ehyfRuZKMgS82rLxg9ismgLR3lZbW-
khGbR2_ouyIUY.js:24:2542

and some mixed content is blocked

Blocked loading mixed active content
“http://www.independent.co.uk/profiles/ines/modules/ines_gigya/js/gigya.validate.js”[Learn More]

Replying to mwolfe:

  1. I clicked on the HTTPS Everywhere button, but did not see "Block all unencrypted requests"

Well it should be there,

https://imgoat.com/uploads/a38a4a9316/87767.jpg

Do you see the HTTPS Everywhere extension icon in your toolbar? If not click on the burger menu and click on Customize at the very bottom and you should be able to move it and place it in your toolbar. Then try again what I suggested to see if it will solve the issue.

Changed 21 months ago by mwolfe

Attachment: jslogindependent.txt added

browser console js

Changed 21 months ago by mwolfe

Attachment: browserlogindependent.txt added

comment:6 Changed 21 months ago by mwolfe

I clicked on 'Block all unencrypted requests' and opened the Brower log. There are 6 options: NET, CSS, JS, Security, Logging, and Server. I copied the JS and Logging and attached the files. Much shorter than before (but more than 5 or 6 lines, a page or two). Also txt, not a Word file.

comment:7 Changed 21 months ago by cypherpunks

The error seems to be this one,

proxy request timeout  gigya.js:21:8574

I'm not going to investigate this further but "proxy request timeout" appears in this link and one would have to look at the surrounding code to know what's happening https://cdns.gigya.com/JS/gigya.js?apiKey=2_bkQWNsWGVZf-fA4GnOiUOYdGuROCvoMoEN4WMj6_YBq4iecWA-Jp9D2GZCLbzON4

comment:8 Changed 20 months ago by mwolfe

Today, I can comment on the Independent without any problem. Not sure if the Independent fixed their website, or if it was Tor 8.a3 (or both).

comment:9 Changed 20 months ago by cypherpunks

Resolution: fixed
Status: needs_informationclosed

Thanks for the followup!

Note: See TracTickets for help on using tickets.