Issue metadata
Sign in to add a comment
|
FTP permission exceptions do not persist |
||||||||||||||||||||||
Issue descriptionVersion: Version 54.0.2826.0 canary (64-bit) OS: Windows 7 What steps will reproduce the problem? (1) Visit ftp://ftp.hp.com/ (2) In the OIB dropdown, choose "JavaScript: always block on this site" and "Images: always block on this site" (3) Refresh the page Observe: OIB setting reverts to allow JavaScript and images (4) Visit chrome://settings/siteSettings/javascript Observe: Exception not listed
,
Aug 12 2016
Is there some reason we /wouldn't/ want FTP permissions to persist? While I'm not super-excited about per-site permissions, I would like to add a BLOCK for JavaScript on ftp://* Related: https://bugs.chromium.org/p/chromium/issues/detail?id=636981
,
Aug 15 2016
I'm curious why you would want to block JS on these pages? The JS that is running is bundled with Chrome right?
,
Aug 15 2016
I'd like to block any JavaScript delivered non-securely, including JavaScript served in FTP-delivered HTML or from FTP-servers, since FTP is a non-secure protocol. The JavaScript of interest isn't bundled with Chrome, it is supplied by the FTP server itself.
,
Aug 16 2016
Ah I see, if you go to ftp://ftp.hp.com/pub/alphaserver/archive/news/index.html for example, you can't disable JS for it. I'd argue that it would be easier to disable JS by default and enable it on https. I know that doesn't fix the hole here but it should be a good enough workaround. We should fix this though, I think we can address it at the same time we address file: permissions.
,
Aug 16 2016
,
Aug 17 2016
Oh, wow, I see now. This feels like it should treated in a similar way to we treat file:// urls.
,
Aug 17 2016
(which I should add we are reassessing as well)
,
Aug 31 2016
,
Oct 19 2016
,
Oct 20 2016
,
Nov 16 2016
,
Nov 22 2016
,
Nov 29 2016
,
Nov 29 2016
,
Dec 5 2016
,
Dec 13 2016
Issue 588722 has been merged into this issue.
,
Nov 10 2017
,
Feb 18 2018
,
Nov 23
***Mass UI Triage*** The UI has changed completely on the latest version as compared to the older version hence archiving. If you have more data to reproduce this bug or have alternate repro steps, please reopen or file a new issue. Thanks! |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by benwells@chromium.org
, Aug 12 2016Owner: raymes@chromium.org
Status: Assigned (was: Untriaged)