Proxy Request aa214ce2-2417-44ea-8d35-6791b3277986
Parent Attack |
d2088f8c-0c0a-456a-bd52-422f12f1c264 |
Date |
2020-09-27 01:09:31PM |
URL |
royaltransports.com.mx/wp-login.php |
Form Data |
["log: royaltransports", "pwd: royaltransportsroyaltransports2013", "testcookie: 1", "wp-submit: Log In"] |
Headers |
["User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:60.0) Gecko/20100101 Firefox/60.0", "Accept: text/html", "Connection: keep-alive", "Content-Length: 88", "Content-Type: application/x-www-form-urlencoded", "Cookie: wordpress_test_cookie=WP+Cookie+check", "Referer: http://royaltransports.com.mx/wp-login.php"] |
<HTML>
<HEAD>
<TITLE>404 Not Found</TITLE>
</HEAD>
<BODY>
<H1>Not Found</H1>
The requested document was not found on this server.
<P>
<HR>
<ADDRESS>
Web Server at royaltransports.com.mx
</ADDRESS>
</BODY>
</HTML>
<!--
- Unfortunately, Microsoft has added a clever new
- "feature" to Internet Explorer. If the text of
- an error's message is "too small", specifically
- less than 512 bytes, Internet Explorer returns
- its own error message. You can turn that off,
- but it's pretty tricky to find switch called
- "smart error messages". That means, of course,
- that short error messages are censored by default.
- IIS always returns error messages that are long
- enough to make Internet Explorer happy. The
- workaround is pretty simple: pad the error
- message with a big comment like this to push it
- over the five hundred and twelve bytes minimum.
- Of course, that's exactly what you're reading
- right now.
-->