Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

6
  • 1
    I guess ssl is a workaround not a code fix. Problems should be fixed at source at best. Commented Mar 5, 2013 at 17:35
  • @asadz: the fact that the application shows the username when it is entered incorrectly is not an application bug, it is intended functionality and does not require a fix imo. Commented Mar 6, 2013 at 9:34
  • @devcity2012 An intended functionality perhaps but poorly thought of; there is a part of requirements analysis in software engineering; this is where these things should be sough preferably using Sequence diagram;how come there is no check for a form before submission? Input validation void ? Commented Mar 6, 2013 at 9:48
  • 1
    If the form takes a username and a password and both are present and then the backend is configured to display the username, that is not an application error if the user mistakingly enters his/her password in the username textfield. Commented Mar 6, 2013 at 9:50
  • I'm talking it as a problem only in a sense where a request would be submitted just based upon user-name field? Commented Mar 6, 2013 at 9:53