- Thread starter
- #1
- Oct 28, 2013
- 1,934
- 838
Hey chill, this is very minor as it will correct itself, but I don't know if it will impact the software later on down the line.
I had a small typo with logging in in the top corner box a couple days ago, so it brought me into the incorrect credentials screen. Rather than using the page-specific fields, I logged in using the corner again. The page returned a "use POST" error and had me re-enter the credentials again. I always asumed that ALL log in fields in professionally made web software were done with POST, but it might be trying to directly input to the SESSION data or something. I was a bit rushed, so I didn't get which line it was on, but it might be worth considering switching out the POST calls for REQUEST calls at some point. If the software does have a discrepancy in it, that would bypass it.
I had a small typo with logging in in the top corner box a couple days ago, so it brought me into the incorrect credentials screen. Rather than using the page-specific fields, I logged in using the corner again. The page returned a "use POST" error and had me re-enter the credentials again. I always asumed that ALL log in fields in professionally made web software were done with POST, but it might be trying to directly input to the SESSION data or something. I was a bit rushed, so I didn't get which line it was on, but it might be worth considering switching out the POST calls for REQUEST calls at some point. If the software does have a discrepancy in it, that would bypass it.
