New https methods requires extra knowledge and config
Posted: Fri Nov 24, 2017 11:31 pm
all of this is erroenus disregard. I leave it here for posterity. see edit
Hi,
I can't seem to add permission rules on this website
http://www.focus-home.com/
I can still add normally on other sites. This URL is different in that it unusually contains a hyphen.
Temporary Allow All works on this URL however.
edit: actually I was coming into the same thing addressed here https://forums.informaction.com/viewtop ... 098#p92098
that's twice I misunderstood the the behaviour of the https lock icon and its associated functions.
originally I thought it was UI indicator I was on a https enabled connection. after that I thought it was a less strict domain matching that Noscript automatically employed upon a click when dealing with a https site, in order the make https sites work, and this was tolerated because https sites were more trustworthy. a behaviour which I could toggle to off to match how Noscript treates non-https sites, if I so chose.
I understand now that the https way is just chosen first and I must toggle it again myself to fix things that don't work. that's kind of sub-optimal I suppose and a step back from a user experience standpoint. that's minor I guess. more importantly it's kind of confusing situation and strikes people as a bug.
Hi,
I can't seem to add permission rules on this website
http://www.focus-home.com/
I can still add normally on other sites. This URL is different in that it unusually contains a hyphen.
Temporary Allow All works on this URL however.
edit: actually I was coming into the same thing addressed here https://forums.informaction.com/viewtop ... 098#p92098
that's twice I misunderstood the the behaviour of the https lock icon and its associated functions.
originally I thought it was UI indicator I was on a https enabled connection. after that I thought it was a less strict domain matching that Noscript automatically employed upon a click when dealing with a https site, in order the make https sites work, and this was tolerated because https sites were more trustworthy. a behaviour which I could toggle to off to match how Noscript treates non-https sites, if I so chose.
I understand now that the https way is just chosen first and I must toggle it again myself to fix things that don't work. that's kind of sub-optimal I suppose and a step back from a user experience standpoint. that's minor I guess. more importantly it's kind of confusing situation and strikes people as a bug.