InformAction Forums

Hi there,

Sorry for this annoying question. I used to be able to make credit card payments online through Bank of Scotland Secure/MasterCard SecureCode (same thing). I'm sure you'll be familiar with it; you'd enter your payment details into a website, then the little box would appear and say "Processing...", then you'd be redirected to a page saying payment was successful.

However, I just refreshed FireFox and reinstalled NoScript, and it doesn't work anymore. It never advances from "Processing...". I've allowed every script on the page (that is, for every retailer's page that uses it) and I've allowed securesuite.co.uk as well, which seems to be the site that it "works" through. I've also allowed bankofscotland.co.uk and MasterCard's sites, for no particular reason except I thought they might be involved.

If I block securesuite.co.uk, then it uses the script-free version, which would work if it weren't for the XSS filtering. I added a whitelist regex for securesuite but it doesn't work (about that I'm not surprised). I also imported my general whitelist from my old FireFox settings, and it still doesn't work (about that I am surprised). Does anybody have any ideas?

Thank you!

Please post any related messages you see in the Browser Console (Ctrl-Shift-J) when it fails.
(if you don't know what's related, turn off CSS warnings and post everything else you see)

Can you also post here the regex that you attempted to use?

Here is the regex, haha. It will be clear that I don't actually know how to make regexes.

^https?://(www.)?securesuite.co.uk\/?([a-z])*

In a bizarre but fortuitous turn of events, it actually seems to be working now (scripts enabled style), despite nothing changing. It worked on "Safe Mode" FireFox and Internet Explorer, but consistently didn't work on FireFox with NoScript enabled. I have accidentally donated to a guide dogs charity -- perhaps the universe intended this all along. Thanks a lot for your help.

wat?

Alexander wrote:^https?://(www.)?securesuite.co.uk\/?([a-z])*

Well, even though I can't understand any of what you're saying in that last post, I at least help you optimize that regex a bit: (You don't need to escape / unless you are enclosing the regex in slashes.)

What you had is not bad for someone who knows nothing of regular expressions though.

This tutorial might help you if you care to learn regular expressions.

Oh, sorry, that was quite garbled!

It seems to be fixed now, even though I didn't change anything. I'm surprised, because the fact that it worked in safe mode and IE seemed to confirm that it was due to NoScript. In the process of trying to generate an error for the log, I accidentally donated to a charity because it actually worked.

Ah, thanks a lot for the help with the regex and the tutorial!

You're welcome, and I hope you think that guide dogs are a good cause.
(Well, I do anyway...)