Describe the bug
When it is the first login, Amazon redirects to a page with an input for a number sent to the phone number of the user.
The page keeps refreshing, and on every refresh, the number is cleared.
I can see that there is a form <form id="pollingForm" method="get" action="/ap/cvf/approval/poll">
and the ajax call for /ap/cvf/approval/poll returns a 302 response with redirection to http://localhost:3000/www.amazon.com/404
Without the proxy, the poll returns 200 OK
Eventually it tries to get www.amazon.com/404 , which returns a 404.
Then, this is triggered:
function handlePollingError() {
window.location.reload();
}
I am investigating and may come up with a solution.
I am getting it from alexa-remote, but I`ve seen it before also on node-red.
To Reproduce
Steps to reproduce the behavior:
Go to the proxy page to login in a machine never logged before, with an account with 2FA enabled
Type user password
Start typing the token from the sms, before finishing it will reload if you are not fast enough
Expected behavior
Do not refresh, token works when login is clicked.
Describe the bug
When it is the first login, Amazon redirects to a page with an input for a number sent to the phone number of the user.
The page keeps refreshing, and on every refresh, the number is cleared.
I can see that there is a form
<form id="pollingForm" method="get" action="/ap/cvf/approval/poll">
and the ajax call for /ap/cvf/approval/poll returns a 302 response with redirection to http://localhost:3000/www.amazon.com/404Without the proxy, the poll returns 200 OK
Eventually it tries to get www.amazon.com/404 , which returns a 404.
Then, this is triggered:
I am investigating and may come up with a solution.
I am getting it from alexa-remote, but I`ve seen it before also on node-red.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Do not refresh, token works when login is clicked.
Screenshots & Logfiles
![image](https://github.com/user-attachments/assets/a3208151-6ead-4ed4-9c5b-0ecdd1c165ef)
Versions:
Latest alexa-remote2
Additional context
Maybe a misconfiguration? I am looking into it.