The Azure Cosmos DB Blog

All about Azure Cosmos DB and Azure

Category: API (page 1 of 8)

Unusual activity on one of my API Apps

I use a product from a former MVP, Thomas Ardal to handle logging from my Azure Web and API Apps.

The product is

Every time there is an error I receive an email like the one shown below.


When I click on the link, I am able to view the detail view from my dashboard

The first thing I noticed is the URL. In this case it is a GET operation with /feed/ for the path.  My API App does not have an operation that has feed in the path.

In the upper right corner there is list symbol with a red star on it.  When I click on it,  I am presented with Quick Fixes for the issue, as shown below.

I want to be able to see where the Request originated from.  I click on WHOIS.  This takes me to dpip where I am able to see the Geo location for the IP Address as shown below

The Security rating provides me with additional information.

Clicking on the Proxy type Tor provides  me with more information,

Without I would not know about issues like this

Configuring my API App was easy.

I don’t usually write product reviews.

I highly recommend you take out for a test drive .

Invalid Swagger from API App – Tip

Have you ever received an Invalid Swagger 2.0 Error for an API App?

If you are returning the standard status codes, you will find that there are duplicate codes.  This is one cause of the error.

If you edit your SwaggerConfig.cs, as shown below, this will solve the problem

 // In accordance with the built in JsonSerializer, Swashbuckle will, by default, describe enums as integers.
 // You can change the serializer behavior by configuring the StringToEnumConverter globally or for a given
 // enum type. Swashbuckle will honor this change out-of-the-box. However, if you use a different
 // approach to serialize enums as strings, you can also force Swashbuckle to describe them as strings.


Older posts
%d bloggers like this:
Skip to toolbar