2.There were no restrictions on user input during the test
Evironment:
Windows XP Professional
Apache
MySQL
PHP 5.4.45
discovered by: mstteam(Linkey)
1.Packet at the login, no encryption

2.There were no restrictions on user input during the test

Evironment:
Windows XP Professional
Apache
MySQL
PHP 5.4.45
discovered by: mstteam(Linkey)
<!-- github-sync-id:238363740 -->
@base64linqi see more --> [stackoverflow](https://stackoverflow.com/questions/2336678/login-without-https-how-to-secure)
<!-- github-comment-id:313596323 -->
just a passerby here You're inspecting a http request over localhost, so it wouldn't be encrypted. Had you say had some type of self-signed cert and accessed https://localhost it would've shown encrypted. It's usually counter productive (key word usually, I'm sure there are some few special reasons for it) to do encryption over HTTP.
~~just a passerby here~~ You're inspecting a http request over localhost, so it wouldn't be encrypted. Had you say had some type of self-signed cert and accessed https://localhost it would've shown encrypted. It's usually counter productive (key word usually, I'm sure there are some few special reasons for it) to do encryption over HTTP.
<!-- github-comment-id:315512844 -->
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
1.Packet at the login, no encryption

2.There were no restrictions on user input during the test

Evironment:
Windows XP Professional
Apache
MySQL
PHP 5.4.45
discovered by: mstteam(Linkey)
The encryption is made at HTTPS level, if you have it. What other type of encryption are you expecting here?
@base64linqi see more --> stackoverflow
well the whole post on stackoverflow is to point out that there is no viable solution so...
just a passerby hereYou're inspecting a http request over localhost, so it wouldn't be encrypted. Had you say had some type of self-signed cert and accessed https://localhost it would've shown encrypted. It's usually counter productive (key word usually, I'm sure there are some few special reasons for it) to do encryption over HTTP.