"Incoming request is not HTTP" error due to missing base path

Products

• Service Virtualization

Issue/Introduction

Seeing multiple errors on Portal for various virtual services with the incoming request is not HTTP.  After count reaching 100, Virtual Service is going to down; looks like this is due to security scans on the assigned ports

Environment

All supported DevTest releases.

 

Cause

The reason for seeing the error is the Virtual Services (VS) are running with HTTP and HTTPS calls are hitting the VS.

The VSs don't have a basepath and any call to the specific port will reach VS. One of the scenario is Scanning tool. At a corporate level when port scans happen which will trigger transactions against VS's.

Resolution

It is recommended to add Base Path to each VS and redeploy.

 

Additional Information

What the base path is in a Virtual Service Model