Comments on: Do not Use Firefox 3 to Make Secure Payments Online

By: Robert

Robert — Thu, 02 Oct 2008 16:52:28 +0000

This is one of the most ridiculous post I’ve ever read. Hahahaha, it’s almost a joke!
I’ll bookmark as funny.

By: larry

larry — Sat, 27 Sep 2008 17:44:26 +0000

I will take my chances getting billed twice for an online payment before I will will I.E. to make a secure payment I E has more holes than a swiss cheese when it comes to anything security related. the only reason most people have it and that it is the most common browser is because #1 mmicrosoft wil. not allow us to use other browsers for windows update. &; I’E’ comes installed with windows. i myself use I.E. ONLY For wwidows update. Anything else I use Fire fox or opera.

By: Mon

Mon — Fri, 08 Aug 2008 13:12:09 +0000

Same thing happened to me, luckily I was using PayPal, it crashed before it got processed… phew!

By: Chris

Chris — Thu, 07 Aug 2008 23:15:43 +0000

“Wouldn’t change to IE even if it would save me from 40 charges”

Jean, you are one stupid bitch

By: Wolf

Wolf — Sat, 19 Jul 2008 05:39:49 +0000

Hrm, much better explaination of the problem in the comment before mine.
“Important things like that should always use _POST_.” (correction) and Firefox’s session restore is smart enough to not resend post information which may result in such duplicate transactions. You should definitely complain to any online retailer who uses GET for forms for such things as the entire query string including your sensitive info is sent in the URL.

By: Wolf

Wolf — Sat, 19 Jul 2008 05:32:16 +0000

Unless you have session restore configured to automatically restore your session, you were prompted and chose to have Firefox reopen your tabs the 2nd time. Being on an SSL website, Firefox naturally, for your security didn’t cache that page and reloaded it, which was unfortunate for your case as reloading the page was a “bad thing”. If you’re concerned about your session being reloaded again, choose the don’t resume option when Firefox prompts you, simple as that.

Its unfortunate you got double-charged and that Firefox crashed. Make sure you send in a crash report so those crashes can be fixed, or passed on to the plugin or addon vendors responsible.

By: Tom

Tom — Sat, 19 Jul 2008 05:28:20 +0000

This is actually an issue with their site, they are using GET instead of POST to process the transaction. Important things like that should always use GET. In fact, google deleted some peoples sites accidentally because they used GET (which is used to download and crawl webpages) instead of POST (which is used to send data to the server properly, like with this comment). You should complain to them about how they use GET instead of POST.

By: Salute Blog » Firefox 3 iyi ama…

Salute Blog » Firefox 3 iyi ama… — Fri, 11 Jul 2008 15:21:38 +0000

[...] ödeme tuşuna bastığında Firefox aniden kapanıvermiş ve bir ödeme yapacakken iki ödeme yapmış. Tabi sonra parasını geri almış orası [...]

By: Madhur Kapoor

Madhur Kapoor — Thu, 10 Jul 2008 13:12:16 +0000

FF does seem to have a lot of Security vulnerabilites. Lucky you got you money back.

By: Jay

Jay — Thu, 10 Jul 2008 13:01:58 +0000

Wouldn’t it be simpler to set Firefox not to reopen webpages after restarting, or am I missing soemthing here?

By: Online ödemelerde Firefox 3 kullanmak sakıncalı mı? | Teknoloji Herşeyim

Thu, 10 Jul 2008 11:53:36 +0000

[...] fakat Firefox 3 kullanarak online bir ödeme yapıp bu çökme problemini teyit etmedim. Ancak Sizlopedia‘nın yazarı, başından geçen ilginç bir olayı paylaşmış. Yazar, LayeredTech [...]

By: blink4blog

blink4blog — Thu, 10 Jul 2008 03:14:28 +0000

sorry for your crash of cash, but i think this is special case, i do online banking and transfer of fund using FF and so far so good since FF3 beta 2.

By: Keith Dsouza

Keith Dsouza — Thu, 10 Jul 2008 01:34:02 +0000

Can be pretty hard on you at times, what I do at times when the browser crashes at a critical time is to check if the order has already been placed or not.

I only order a second time after I have confirmed that my card has not been charged, even though it may take a few hours to confirm that.

By: moin

moin — Thu, 10 Jul 2008 00:00:43 +0000

:O firefox mysteries are taking dark sides day by day

By: Ray B

Ray B — Wed, 09 Jul 2008 20:05:57 +0000

So you recommend using IE ,
(the browser with the worst security history)
http://news.cnet.com/8301-13554_3-9984277-33.html

over Firefox (the most secure )
http://www.crn.com/security/208802248

just because the site you accessing doesn’t properly handle duplicate transactions ?

So what you are saying is you would rather have your sensitive information stolen than risk possible duplicate ( 1 time) charge?

By: HitMan

HitMan — Wed, 09 Jul 2008 18:41:12 +0000

As “OP Dave” mentioned every site that includes a system for online payments should be aware of such things such as crashes, duplicate submits and other USER inputs that might alter the transaction, in your case by charging you twice.

@Dj Flush: Why did you restored your session after the crash? You could checked with the company if the order process was okay after the crash and if not, do it again :>

For me, working everyday with FF3 and having lot of tabs opened i have expirienced a small amount of crashes. After all, most of Firefox crashes in the previous versions had to do with some Addons that messed up with the rendering engine of the browser. ( Firebug was one + Yslow another! )

By: Dj Flush

Dj Flush — Wed, 09 Jul 2008 16:40:48 +0000

@David Peterson

For me Firefox 3 crashes ten times more as often as Firefox 2.

I hope at least someone agrees with me.

By: Davin Peterson

Davin Peterson — Wed, 09 Jul 2008 15:21:13 +0000

I have noticed that Firefox 3 has crashed more often than Firefox 2.

By: Dj Flush

Dj Flush — Wed, 09 Jul 2008 14:47:31 +0000

The best wise thing would be to keep myself on the safe-side on the first place and for that I certainly have to use a browser which does not crash while submitting forms.

By: OP Dave

OP Dave — Wed, 09 Jul 2008 14:39:38 +0000

Duplicate charges for the same transaction are 90% the fault of the site which processed your on-line charge: not your browser.

There should always be a provision in the card-processing software to reject duplicate charges for the same transaction/invoice.