search

gorhill / httpswitchboard

Point & click to forbid/allow any class of requests made by your browser. Use it to block scripts, iframes, ads, facebook, etc.
GNU General Public License v3.0
1.33k stars 84 forks source link

Issues with Chrome 39.0.2159.4 dev-m (64-bit) #415

Closed puff-m-d closed 10 years ago

puff-m-d commented 10 years ago

Hello,

With the just released Chrome 39.0.2159.4 dev-m (64-bit), I have had to modify almost all of my recipes for sites. I experienced the same issue reported in # 414 (https://github.com/gorhill/httpswitchboard/issues/414). Most were fixed by allowing the "other" category in the matrx (but not all). Something must have changed in the latest dev Chrome version which has changed what HTTPSB sees for a site.

An example is for http://www.majorgeeks.com/ where I had to now allow the "other" for the site. Here are some of the new items in the logs that are showing up: 10:08:45 AM other http://www.majorgeeks.com/index.php?ct=core&action=tasks 10:08:45 AM other http://www.majorgeeks.com/images/news.gif 10:08:45 AM other http://www.majorgeeks.com/images/mg_wayoff.gif 10:08:45 AM other http://www.majorgeeks.com/images/mg_offbase.gif 10:08:45 AM other http://www.majorgeeks.com/images/notepad.gif 10:08:45 AM other http://www.majorgeeks.com/images/mghot.gif 10:08:45 AM other http://www.majorgeeks.com/images/mgnew.gif

I have just recently started using HTTPSB and am still learning and hope that this post makes sense. i apologize in advance if my explanation is not very good and if you need further information, please let me know. I do not know if this is an issue but something has definitely changed.

Best regards, Kent

gorhill commented 10 years ago

As said in the front page of HTTPSB, I expect the extension to work flawlessly on stable version of Chromium-based browsers. Chrome 39 dev is not a stable release, and clearly the latest version of Chrome 39 dev has serious issues, and this needs to be reported to Chromium devs so that they fix it. It appears the browser is now reporting request of type image as request of type other. This needs to be fixed by Chromium devs.

puff-m-d commented 10 years ago

Hello gorhill,

Thanks for the speedy reply. I encountered this issue yesterday and just made the necessary changes in HTTPSB, then moved on. I initially was not going to report it here since it was an issue with a dev version of Chrome but saw issue https://github.com/gorhill/httpswitchboard/issues/414 and decided that I would. I am not familiar with bug reporting to Chrome but will proceed in trying to report this to the Chrome dev team.

Thanks again...

gorhill commented 10 years ago

I tried, and I see that GIF and JPG images are wrongly reported by the Chrome 39 dev, while PNG are properly typed. In my previous attempt I didn't notice my other column was in allow mode.

gorhill commented 10 years ago

I will mark this one as dup of #414. I appended the problem reported here to a similar issue I opened a while ago with Chromium devs, so maybe no need to file a new issue. There has been no feedback so far on that issue though.

puff-m-d commented 10 years ago

Hello,

For the record, this issue involving "images and others" is fixed here on the latest Chrome 39.0.2171.2 dev-m (64-bit) that was released today. It not only solved the issue with HTTPSB but also uBlock is working correctly again. I guess the real test will be it will stay fixed in the next release or not since there is no update on the issue gorhill reported here: http://code.google.com/p/chromium/issues/detail?id=410382#c1 . That makes me think it may just be a coincidence that it is fixed.

puff-m-d commented 9 years ago

Hello,

For the record, an update... Just like I had previously thought in my last post, the issue with "images and others" that had been fixed with Chrome 39.0.2171.2 dev-m (64-bit) seems to be a coincidence as I was afraid of as it has reappeared in the latest Chrome 40.0.2182.3 dev-m (64-bit) that was released today. I also noticed that http://code.google.com/p/chromium/issues/detail?id=410382#c1 is still open and it appears they may be making progress, albeit it slowly...

puff-m-d commented 9 years ago

This is just an observation so it may or may not have anything to do with the issue...

The issue seems to come and go with different versions of Pepper Flash. In Chrome 39.0.2171.2 the issue went away and Flash was updated in this version to 15.0.0.152. In several following releases of Chrome the issue remained fixed and the version of Flash did not change. Today when Chrome updated to 40.0.2182.3, Flash was also updated to version 15.0.0.189.

I do not have the information to support this but the issue first appeared to me with Chrome 39.0.2159.4 dev-m (64-bit). If my memory serves me, Flash was also updated with this release of Chrome (I am about 99 % sure of this)...

This may be just a coincidence but I am starting to think this may very possibly be related to the different versions of Flash. Just a thought...

P.S. I would have posted this to the chromium devs but I refuse to have an account with Google...

gorhill commented 9 years ago

I think you should share the details of the problems you experienced in the Chromium issue thread.

Do you install HTTPSB manually or from the store? I just checked-in a workaround for more image types/css.

puff-m-d commented 9 years ago

I installed from the store...

I will post to the Chromium issue thread soon but I will have to open a dreaded Google account first. I will do this as soon as I have the time (hopefully later today)...

gorhill commented 9 years ago

I will have to open a dreaded Google account first

Just give me the details here, I will transcribe them onto the thread.

puff-m-d commented 9 years ago

Hello gorhill,

Thanks for the offer but I remembered that I had an old, forgotten Google account from back when I used to have an Android phone, so I went ahead and posted my observations to the Chromium issue thread (Issue 410382) here: https://code.google.com/p/chromium/issues/detail?id=410382 post # 30. I am not very code savvy like most over there, but I posted my observations as best I could... HTH...

puff-m-d commented 9 years ago

Hello,

FYI Update: Just posted at https://code.google.com/p/chromium/issues/detail?id=410382 post # 31:

[Quote] An update on my post # 30 above...

Today Chrome 40.0.2188.2 dev-m (64-bit) was released and Flash was not updated (still version 15.0.0.189). The issue in this thread is fixed again with this version of Chrome, so I guess this answers my question about coincidence (Flash appears not to be involved).

I am not tech savvy enough to do "bisects" and I do not use the canary versions (only use the released 64-bit dev versions on Windows 8.1.1). I can offer the following observations though: Prior to Chrome 39.0.2159.4 dev-m (64-bit) - No Issues. With Chrome 39.0.2159.4 dev-m (64-bit) - Issue first appeared on my system. With Chrome 39.0.2171.2 dev-m (64-bit) - No Issues. With Chrome 40.0.2182.3 dev-m (64-bit) - Issue reappeared, broken again. With Chrome 40.0.2188.2 dev-m (64-bit) - No Issues..... I hope this may help to narrow down whatever it is that keeps breaking and then fixing as far as this issue is concerned... [/Quote]

Just hoping this information may help them with this reappearing issue...