1907735 - "Resend code" button from PayPal login form doesn't end up sending an SMS in Firefox, but does in Chrome

Status: UNCONFIRMED

(Web Compatibility :: Site Reports, defect)

Description

[markballew]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:127.0) Gecko/20100101 Firefox/127.0

Steps to reproduce:

recurring issue with form post requests from website forms to some server side platform, platforms vary, but I have experienced this issue over a long period of time, there is some short issue that I "believe" is related to the length of the string being posted. last 2 events experienced on paypal and etrade. My concern here is that now when I talk to a corporate customer support agent, they are now immediately associating their issues with Firefox, this is a VERY REALLY bad thing to have developing in the public opinion of Firefox. The support agents always direct me to use Chrome. The engineer team needs to deal with this, is it that Firefox is following standard and Chrome team has found a way to make Firefox look bad, I don't know, but I would not put it beyond Google to attempt to sabotage this project., it just means too much money to them. I do honestly with 30 years experience believe the root cause is the concatenated string length not passing and being committed into the server side platform.

Actual results:

On post of form data down-stream process fails in firefox but passes in chrome. the most recent clear case is paypal. Attempt to pay invoice received in gmail, open link to paypal invoice, use paypal pay method 'paypal' or 'pay later' , receive popup to connect to my paypal account via a sms authentication. sms code is never received, usually a user may have to client the manual 'resend code' and paypal system will recognize the request and send, but this time I tried many times and variations and never received code. I don't believe this is fully a paypal server side issue as I then logged in with chrome and performed the same task, as usually i had to 'resend code' manually, but I did receive the sms, as I have in the past. I don't know if there is a security risk here, so I won't check the Security button below.

Expected results:

I should have received sms code after the manual 'resend code', this has always worked.

Comment 1

[markballew]

I didn't know what category of issue to assign, I don't see anything that closely matches, please assign appropriate category for me, thanks.

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The Bugbug bot thinks this bug should belong to the 'DevTools::Netmonitor' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Comment 3

[Nicolas Chevobbe [:nchevobbe]]

Hello Mark,
How do you know that it's POST requests that are failing? Can you give the URL of the request that do fail?
I'm using PayPal myself quite frequently and I do receive the SMS code, so I'm wondering what the issue could be here

Comment 4

[markballew]

It's not just paypal, I am experiencing this issue on other platforms. maybe the best thing to do is help me capture a good log for you to look at, can you point me to how I should do this, as I am usually logged into a secure site when issue occurs. What prompted me to return to this thead was that i hit a issue with accessing content on etrade via an basic html link which was supposed to open a html dialog and display basic textual content, however the read never completed, when i performed same in Chrome it was successful. Also logged another issue that was more general but it all seems to be in most cases when I submit a secure form in a secure environment, the target server side process does not successfully handle and process the request, I can't see the server side obviously, but I am told again by etrade customer service it is a common issue and they are always recommending clients to use Chrome or Edge, so logically there is some paradigmatic issue not being addressed by firefox team. If it is my settings causing the issue with all plugins disabled, then the seeded setup in firefox should be addressed by development, if it is firefox failing on a standards protocol and Chrome and Edge are not, then engineers should find out why and get off the horse and fix it. But this is pervasive and long-standing and a huge part of the reason users community is declining. I came to use Firefox a very long time ago but when the engineering team decided to move to a rapid rollout of incremental change and leave the 3rd party developers in wind i switched to Chrome because I needed the plupings/extension to do my work, but I did return to using Firefox in combination with Chrome, Chrome for work, and Firefox for personal, but now I feel like I"m being forced to make a choice to mover everything to a chrome based browser solution. So to help I will try to capture a log, if you direct me to some a page that tells me how to get what you need.

Comment 5

[Dennis Schubert [:denschub]]

Is this still happening to you today?