Problems with weather.com on Fx again.

[deleted]

Can I get a link to it?

here link for stable build: http://download.adguard.com/setup.exe

 

[streetwolf]

Thanks. Why is the stable setup file so much larger than the beta setup file?

 

[deleted]

Thanks. Why is the stable setup file so much larger than the beta setup file?

IDK stable is only 12.3 MB and beta 12.4MB, not much diff I guess
(unless its d/ling .net)
BTW did it fixed your problem?

 

[streetwolf]

I just installed the stable version. I see it is 2037.6352. Keep in mind that things were working fine with the betas until some point about a month or two ago. If the stable version corresponds to a beta that didn't work then the stable version probably won't either. I'll have to wait a little bit to see how the site behaves. Will get back.

---------- Post added at 11:42 AM ---------- Previous post was at 10:30 AM ----------

Things seem to be more up to date with the stable version. I still get some out dated stuff occasionally. For instance at this moment the 'next few hours' graphic starts at 11:45 am. Sometimes it will say 11:30 am. Refreshing the page doesn't work but getting out of the page and then selecting it again usually gets the time right. Even so what I am seeing is a big improvement over the betas I've been using. I'll go with the stable version for a little longer and see how things play out at which point I might try the beta again.

---------- Post added at 11:59 AM ---------- Previous post was at 11:42 AM ----------

Still getting different times and forecasts especially compared to IE11.

 

[avatar]

Guys, the problem is not in stable or beta versions.

It's just how weather com server works.
For some unthinkable reason it returns wrong cached response in case of AG is enabled.

What we change in request is Accept-Encoding header, but it shouldn't influence.

 

[streetwolf]

Andrey... At this point I have no idea who is at fault. Earlier today I booted into Safe mode and still had the same weird results even on IE11. I am current playing around with various weather.com cookies.

---------- Post added at 05:52 PM ---------- Previous post was at 05:50 PM ----------

So far the only 100% sure fire way to get the correct results is to disable my Fx cache. I'm hoping the problem might be a cookie, we will see.

 

[avatar]

I am pretty sure the problem is in ETags they use for caching.

Wait for Firefox version of our Stealth Mode add-on and we'll be able to check if i am right

 

[streetwolf]

I also have a similar problem with the weather on cnn.com. The time is often incorrect. This is also 'fixed' when running without a disk cache. Do you have a version of the Stealth Mode add-on I can try right now even if it's an alpha?

 

[avatar]

Do you have a version of the Stealth Mode add-on I can try right now even if it's an alpha?

Not yet ready, next week should be.

 

[streetwolf]

Andrey...

Firefox has this feature called network predictor which predicts what you are going to click on I think. It's supposed to speed things up. I believe it stores it's predictions in the disk cache. I found this in the cache. Anything that might help solving my problem?

Key: predictor-origin:http://www.weather.com/

Cache entry information
key: http://www.weather.com/
fetch count: 7
last fetched: 2015-06-30 15:47:41
last modified: 2015-06-30 15:47:04
expires: No expiration time
Data size: 0 B
Security: This document does not have any security info associated with it.
predictor::seen: 1
predictor::http://injections.adguard.com/: 1,6,1435693616,0
predictor::http://tags.crwdcntrl.net/: 1,3,1435693616,0
predictor::http://www.weather.com/: 1,6,1435693616,0
predictor::http://c.amazon-adsystem.com/: 1,3,1435693616,0
predictor::http://s.w-x.co/: 1,3,1435693610,0
predictor::http://ajax.googleapis.com/: 1,3,1435693616,0
predictor::http://rtax.criteo.com/: 1,3,1435693616,0
predictor::http://ad.crwdcntrl.net/: 1,3,1435693616,0
predictor::http://aax.amazon-adsystem.com/: 1,3,1435693616,0
predictor::http://dsx.weather.com/: 1,6,1435693616,0
predictor::http://triggers.wfxtriggers.com/: 1,3,1435693616,0
predictor::http://fonts.googleapis.com/: 1,3,1435693616,0
predictor::http://cdn.taboola.com/: 1,3,1435693616,0
predictor::http://cdn.gigya.com/: 1,3,1435693616,0
predictor::http://fonts.gstatic.com/: 1,2,1435693606,0
predictor::http://gima.weather.com/: 1,3,1435693616,0
predictor::http://dev.virtualearth.net/: 1,1,1435693606,0
predictor::http://g3.imwx.com/: 1,2,1435693606,0
predictor::http://g1.imwx.com/: 1,2,1435693606,0
predictor::http://g2.imwx.com/: 1,2,1435693606,0
predictor::http://g0.imwx.com/: 1,2,1435693606,0
predictor::http://tags.tiqcdn.com/: 1,4,1435693616,0
predictor::http://www.googletagservices.com/: 1,4,1435693616,0
predictor::http://odc.weather.com/: 1,2,1435693616,0
predictor::http://h.nexac.com/: 1,2,1435693616,0
predictor::http://b.scorecardresearch.com/: 1,4,1435693616,0
predictor::http://secure-us.imrworldwide.com/: 1,2,1435693616,0
predictor::http://c2.taboola.com/: 1,2,1435693616,0
predictor::http://partner.googleadservices.com/: 1,2,1435693616,0
predictor::resource-count: 1
predictor::http://gscounters.us1.gigya.com/: 1,1,1435693616,0

 

[Boo Berry]

You can try disabling it in about:config by toggling network.predictor.enabled and see if that helps any.

 

[streetwolf]

At first it looked like it was working then I started getting old stuff again. I opened up a Bug Report on my problem and asked if the network predictor could be the culprit. A Developer said it's unlikely as the URLS are not used to go anywhere.

 

[streetwolf]

I added this to my user filter and it seems to have 'fixed' my update problems so far... @@||weather.com$document. Been testing for about an hour which should be enough time

On the other hand IE11 is now missing a lot of stuff including ads.

---------- Post added at 01:19 PM ---------- Previous post was at 12:53 PM ----------

I'm now trying this rule to eliminate some ads... @@||weather.com$urlblock

---------- Post added at 01:36 PM ---------- Previous post was at 01:19 PM ----------

@@||weather.com$urlblock doesn't help.

 

[avatar]

It is very unlikely that network.predictor has something to do with that.

Are you sure @@||weather.com$document helps?
I remember that we've already tried that and it didn't help.

 

[streetwolf]

I was running with the rule for over an hour and everything updated as it should. Of course having all those pesky ads really slowed down the site. At this point I think it is easier to find another weather site ;-).

I did open a bug report on my problem. I didn't mention anything about AG though. Here's the link if interested.... 1178720 – Weather.com appears to use old cache data for it's forecasts

---------- Post added at 09:29 AM ---------- Previous post was at 08:35 AM ----------

Got a question for you. When I use the rule @@||weather.com$document I get more ads then when I disable AG protection. Why is this?

 

[avatar]

Got a question for you. When I use the rule @@||weather.com$document I get more ads then when I disable AG protection. Why is this?

Hm, I would say that it's impossible.

 

[streetwolf]

Yesterday I was getting a kind of weird ad but today the ad isn't present anymore. I assumed the ad was still there today. So you are right

---------- Post added at 01:54 PM ---------- Previous post was at 12:16 PM ----------

I don't know if we ever agreed that AG was at fault but I am more convinced every day. For example, I just went to the site and it had times and forecasts that were hours ago. I kept going back to the site with no updates. A site refresh didn't work. I then disabled AG, restarted Fx, went to the site and all is up to date. With AG enabled once more it will fail to update once more.

I looked at the page source and saw that it started with 11 empty lines. Is this OK? I don't ever recall looking at any page that had empty beginning lines.

 

[streetwolf]

I'm not giving up on this. I basically shutdown AG and it's service. I then installed the latest uBlock Origin add-on. I've been running for an hour and weather.com is performing like it should. All times and forecasts are up to date.

IIRC I tried uBlock before and it was giving me the same problems as AG. However, uBlock now has an option, which is checked, to disable Link prefetching. Link prefetching is the default in Fx so it has been enabled all the time. Could link prefetching be the problem? It does grab things from the cache to speed things up. I'll have to try AG with link prefetching disabled and see what happens.

---------- Post added at 06:15 PM ---------- Previous post was at 05:19 PM ----------

I just turned on link prefetching while running under uBlock. Sure enough I started to pull in old pages with old forecasts. After disabling it the forecasts were once again up to date. Very Interesting. Can't wait to try it with AG.

---------- Post added at 07:03 PM ---------- Previous post was at 06:15 PM ----------

Crap. Disabled link prefetch and fired up AG again. Still got old pages.

 

[Boo Berry]

Using @@||weather.com$document will disable all ad blocking, injection, etc.

 

[streetwolf]

Yes, that filter will make things right but it is not the answer. On my system AG is the culprit for my problems with weather.com. I'm concerned that other sites are also displaying old cached pages.