Warp requests hit the application port instead of LittleProxy`s one

Warp observer intermittently fails while inspecting the requests with:
"There were no requests matched by observer [containsParameter(XXXX)] ".
The technical reason for the failure is that the client request hits the original (application server) port and not the LittleProxy`s one (HTTP successful and failed traffic is attached showing the HTTP requests going to the wrong port, i.e 8080). Since Warp hooks into the client/server conversation providing its own implementation of HttpFiltersSourceAdapter in DefaultHttpFiltersSource, while expecting the payload request from client after setting up a WarpContext, the Warp runs into timeout because of the HTTP request never reaches the LittleProxy.