InformAction Forums

Thanks to Noscript, my attempt to purchase from 4allmemory.com was blocked in such a way as to leave $60 from my paypal account in limbo.

Noscript was nice enough to allow virtually the entire transaction to go though, but when I was to be redirected from paypal.com back to the vendor website, Noscript claimed to block an XSS attempt, and so 4allmemory.com didn't get the order--despite the fact that I've already paid through paypal.

Now I have to find some way to stop or reverse that payment. I may have to wait a week or more before I can change the payment's status. I've contacted 4allmemory.com, and they say I should order again--something that I can't do until I find out the status of the $60 I've already paid them.

This is the umpteenth time Noscript has blocked one of my purchases, but this time it was the worst. I promised myself that after this, I would do two things: permanently disable "XSS protection" in Noscript, and complain to Giorio Maone.

Firefox 3.5.6 (Linux)
Noscript 1.9.9.45

Thanks for your feedback.

1. If paypal.com was in your whitelist (and I'm reasonably sure it was, since you're an user of it), you shouldn't have get any XSS warning. Since you did, I would have preferred to see its details logged in Tools|Error Console (or Options|Show Console from the XSS notification), so I could try fix it.
2. When something like that happens, there's a simple work around. On the XSS notification bar, click the Options button and select "Unsafe reload": the transaction will complete nicely with no side effect
3. If your Paypal account has been charged, you should have a transaction ID in your account history and so should 4allmemory.com. Furthermore, you should both have received a mail notification from Paypal. So 4allmemory.com refusing to recognize your payment (or to just refund it, which is matter of two clicks and is entirely free of charges, and let you repeat your order) seems quite unreasonable to me

However, sorry for your hassle. I'll try to order a memory module for my notebook in order to check if I can see what triggers the message and if it can be worked around in a future NoScript version.

I'm sorry about my initial complaint. I don't remember placing paypal.com into my permanent whitelist before the transaction started, IOW, it may have been user error.

Thank you for mentioning the "unsafe reload" option; I'll remember that in case this happens again.