William,
Hi, I think we were at cross-purposes during our phone call.
I had expected you to send me an alternative link for accessing the lloyds bank web-site where
your web 'code' was improved to prevent this problem.
I have updated to the latest noscript add-on, but this did not modify the error I see.
which occurs because the
secure.lloydsbank.co.uk accesses marketing.lloydsbank.co.uk,
and the noscript mechanism will trap and stop this in its default configuration
I had not said but I do have a workaround which is to supply the following config to
noscript
[pictureof noscript config]
but my contention is that security on the site is reduced by having this reference,
Even with this workaround access to the web-site remains slow (which I think maybe
caused by the reference).
Also, as discussed other banks x/y/z do not have websites
with such problems, with data from multiple sites.
Could you send me the original email you had had from IT/security support... ?
what was their rationale to send a noscript web link ? maybe they also have a
response to my new comments above ?
Regards, Paul