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 83 forks source link

chromium-39.0.2159.4 breaks image loading #414

Closed octoploid closed 10 years ago

octoploid commented 10 years ago

With chromium-39.0.2159.4 all images on all webpages get blocked. 39.0.2145.4 was fine.

gorhill commented 10 years ago

Did you look into the request log to find out the request type of images?

octoploid commented 10 years ago

jpegs.

gorhill commented 10 years ago

The request type reported by the browser (under the what column header), not the request type as per path suffix.

octoploid commented 10 years ago

Sorry. I've deleted 39.0.2159.4 and switched back to previous version. So I cannot answer your question. I looked in the error console and it said "blocked by extension" for the images.

gorhill commented 10 years ago

Can't reproduce.

gorhill commented 10 years ago

Actually, my mistake, I didn't realize my other column was in allow mode.

So it appears that GIF and JPG images are wrongly reported by Chrome 39 dev, while PNG are properly typed. This is something to report to Chromium devs. I could theoretically put in a hack to transpose the wrongly typed requests into properly typed ones, but we are talking about an unsupported version of a browser here, I rather keep HTTPSB as clean as possible by supporting only stable releases, as stated on the front page of the project.

octoploid commented 10 years ago

I don't have (and don't want) a Google account. Lets hope someone else also hits this issue and reports the bug to the Chromium devs.

Thanks.

gorhill commented 10 years ago

I appended to a similar issue I already opened a while ago: http://code.google.com/p/chromium/issues/detail?id=410382#c1

ghost commented 10 years ago

unrelated: but how come you pasted that above link as http instead of https (although it does redirect, for me, to https - maybe because of https everywhere extension - currently in firefox)

gorhill commented 10 years ago

No, I am also redirected to https. I just upgraded to Linux Mint 17, hence Chromium 37 -- I was on Chromium 34 before now. I went to check with my previous installation, but Chromium doesn't launch anymore, probably because I am reusing the same profile and it's not forward compatible.