Loading Profile...
Twitter,
Facebook, or email.
The website of our helpdesk tool (which is from www.topdesk.com) becomes extremely slow when used over https. Disabling ghostery (blocking off) fixes it, but whitelisting the site does not. Running the site over http makes it better, but still too slow.
There are no blocked items on the site. I use version 2.4.1 of ghostery
I’m
sad
-
Peter, I'm afraid without seeing the actual software its a bit hard to say why Ghostery would be affecting the site. Does this site load a lot of sub-pages or images?Comment
-
-
It doesn't load much images, but it does load a whole lot of javascript. I understand why it would be slow with ghostery running and not whitelisted, but I would expect that when a site is whitelisted, it would be handled the same as when ghostery is disabled. Does ghostery still inspect everything on a site even when the site is whitelisted?
-
Peter, scanning on the whitelisted domain is stopped, so maybe the domain the JS is being loaded through isn't the same as th domain you've whitelisted (happens a lot whn a CDN is used, a new subdomain is used in then)? Try whitlisting it as well, separately in Ghostery options and see if this improves performance. Also, if you dont mind we could do a remote TeamViewer session so I could take a look at whats happening?
-
-
-
-
-
I've looked at the request the site is doing but they are all going to the same server in our network (using the same hostname).
Unfortunately, a shared session will not be possible due to our securtity regulations. If there is anything else I can try let me know (is there a log possible for the actions of ghostery?)-
Err, Peter, I have to back up my claim on the whitelisting working appropriately: There is a bug currently in the Ghostery v2.4.1 that ignores any whitelisting settings for an HTTPS site :(.
That said, the fix is relatively straight forward, so there are 2 options for you:
1. Wait until I release next version that fixes this issue (I will release it into AMO this week)
2. If you're proficient enough in JS and locating a file in your OS, I could gve you the patch instructions. Its a one line changer.
Let me know. -
-
-
-
-
I’m
thankfull
Ah, that's great (not that there is a bug, but that you found it and can fix it).
I don't know much about JS, but I think I can manage. I'm willing to try the patch.-
Ok, so here are the instructions. =)
First, you will need to find the extensions directory of your Firefox, open: about:support in the URL of your Firefox and then click on the Open Profile Directory next to the Profile Directory.
Once open, navigate to extensions folder, and in it, to firefox@ghostery.com folder and finally into components folder.
You need to edit file called ghostery-content-policy.js. Make sure to make a backup of this file before editing.
Open this file in a text editor of your choice and locate this text:
if (requestOrigin.scheme === 'http') {
delete it and replace with this:
if ( (requestOrigin.scheme === 'http') || (requestOrigin.scheme === 'https') ) {
Save, close editor, restart Firefox and you should be golden. v2.4.2 will fix this, and its slotted for release this week. -
-
-
-
-
I’m
frustrated
Ghostery blocking has to be turned off in order to use the Citibank site properly. White listing the site doesn't help.
This reply was created from a merged topic originally titled
Citibank site doesn't work even with whitelisting..-
the.note.box, is the site you are using listed as HTTPS?
-
-
Received comment from Felix Shnir, an employee of Ghostery, Followed suggested change to ghostery-content-policy.js. Didn't help.
-
-
-
-
-
I’m
excited
I've implemented the given change and the site is working wonderfull now. Problem solved !
-
-
I’m
thankful
My site started to respond to the change today and works now.
Why it didn't work initially I don't know. -
-
I'm glad your issues are resolved. The v2.4.2 is currently sitting in queue for approval in AMO. Feel free to upgrade when it comes out -- it includes the HTTPS whitelisting bug fix.
-
CHAMP
