3 ms·
Believe it or not, I have seen the same problem on an insurance website for a very large insurance company. The issue was that the developers were storing the r
by pkphilip 3y ago
Believe it or not, I have seen the same problem on an insurance website for a very large insurance company. The issue was that the developers were storing the rates in session variables and so when you open a new product in a separate tab with a different rate, it would overwrite the session variables with the rates for the newly opened product.
Then when the user went to the previous tab to purchase the product they ended up buying it at the rate for the product opened in the new tab.
It is amazing that this mistake wasn't caught for a long, long time.
- echoangle 3y agoI hope they didn’t store the literal rate, but only the selected product id, in the session. Otherwise, you could just modify your request and set a low rate…
- pkphilip 3y agoNope. They stored a WHOLE RANGE of fields which was also used to display the rates directly to the customers. A total mess!
- disgruntledphd2 3y agoYeah, I had this problem with the world's only ultra-low-cost airline. We were working on an analytics system and this sortof stuff was pervasive. The entire frontend basically didn't handle multiple tabs. Mind you, this was in 2012, I assume they've fixed it by now.