My Sharona Posted February 7, 2021 Posted February 7, 2021 What would be the login method? GET, POST or Plain HTTP? TYIA
Nathan Explosion Posted February 8, 2021 Posted February 8, 2021 (edited) POST Are you having an issue with the crawler not being able to login, possibly due to CSRF protection? Edited February 8, 2021 by Nathan Explosion
My Sharona Posted February 8, 2021 Author Posted February 8, 2021 (edited) 9 minutes ago, Nathan Explosion said: POST Are you having an issue with the crawler not being able to login, possibly due to CSRF protection? Thank you for the response, Nathan. I don't know that I am having a login issue outside of having the wrong login parameter. I initially thought it would be POST but didn't understand why, for both POST and GET that they want an 'equals' parameter for both. When choosing, "Plain HTTP", the 'equals' goes away so I thought it must be that. What is the purpose of the 'equals' for the password and username and should the respective parameters be the same for both sides of the equations? Edited February 8, 2021 by My Sharona
Nathan Explosion Posted February 8, 2021 Posted February 8, 2021 "auth" = the username of the account, "password" = the password for the account. My Sharona 1
My Sharona Posted February 8, 2021 Author Posted February 8, 2021 Thank you, Sir. Much appreciated. I shall afix the parameters to what you have above.
My Sharona Posted February 10, 2021 Author Posted February 10, 2021 Just a minor follow up here @Nathan Explosion. I don't see where the crawler has logged in (no IP associated with the account). Should a "submit" parameter be included as well? Something like: _processLogin = elSignIn_submit TYIA
Nathan Explosion Posted February 10, 2021 Posted February 10, 2021 What I posted is what should be used. 2 minutes ago, My Sharona said: _processLogin = elSignIn_submit _processLogin = the NAME of the button on the login button on the login page. usernamepassword = the VALUE of that button elSignIn_submit is the ID for that same button - if you do what you are suggesting it is telling Google to add set the value of _processLogin to elSignIn_submit, which is not going have any effect. The crawler probably tried to login and got a CSRF key - you can read the full background to all this information in My Sharona 1
My Sharona Posted February 10, 2021 Author Posted February 10, 2021 1 hour ago, Nathan Explosion said: What I posted is what should be used. _processLogin = the NAME of the button on the login button on the login page. usernamepassword = the VALUE of that button elSignIn_submit is the ID for that same button - if you do what you are suggesting it is telling Google to add set the value of _processLogin to elSignIn_submit, which is not going have any effect. The crawler probably tried to login and got a CSRF key - you can read the full background to all this information in Duly noted. Thank you again sir.
Recommended Posts