ASP Net Core - Server receives multiple GET requests repeatedly

Question

ASP Net Core - Server receives multiple GET requests repeatedly

Navigation

#1 by (1 votes)
#2 by (0 votes)

0

Hello, I have a server hosted on an EC2 instance, Ubuntu Server on Amazon AWS. No one is performing requests to this server, however, logs displayed in CloudWatch indicate multiple GET operations followed by POST, below are operations that are repeated indefinitely:

[6/9/18 4:22:14 AM] Information: Request starting HTTP / 1.1 GET   http: // MY EC2 PRIVATE IP -

[6/9/18 4:22:14 AM] Information: Executing action method   Api.Controllers.InitialController.HelloWorld (Api) with arguments   ((null)) - ModelState is Valid -

[6/9/18 4:22:14 AM] Information: Executing ObjectResult, writing value   Microsoft.AspNetCore.Mvc.ControllerContext. -

[6/9/18 4:22:14 AM] Information: Executed action   Api.Controllers.InicialController.HelloWorld (Api) in 0.1211ms -

[6/9/18 4:22:14 AM] Information: Request finished in 0.2695ms 200   application / json; charset = utf-8 -

[6/9/18 4:22:33 AM] Information: Request starting HTTP / 1.1 POST    link SOMETHING / client / a> application / json 116 -

[6/9/18 4:22:33 AM] Information: Request   finished in 0.3534ms 404 -

Repeat ...

These operations are repeated indefinitely, all the same as above, I want to understand what is happening, if it is a mistake in my server's programming, in addition, understand why it is performing a POST after a GET. How do I fix this?

Thank you

c# asp.net asp.net-core aws ec2

asked by anonymous 09.06.2018 / 06:45

2 answers

ASP .NET - Local file directory using Chrome Receive notice on the cell phone via sms

score 1 · Answer 1

Try to capture the source IP address of these requests, they can be thefts, as said by Julio, but it can also be some Load Balance configuration to check if the service is active (in the case of get), already in the case of the request POST, you can see something about samsung cloud print, it may be that someone has set up some printer on that same ip and the service is still "pinging" to verify the activity, try changing the ip address of the EC2 to verify that these requests continue. If you diver some linked DNS, change the IP but do not change the DNS, if you stop the flames, change the DNS to the current ip, if the calls come back, it may be someone calling directly on your configured DNS address.

score 0 · Answer 2

It's hard to know exactly, but beware, unexpected traffic can be from thefts, malicious or otherwise. AWS Web Application Firewall can help by creating exclusion rules and other protections. See a reference implementation: link