Warp requests hit the application port instead of LittleProxy`s one ------------------------------------------------------------------- Key: ARQ-1952 URL: https://issues.jboss.org/browse/ARQ-1952 Project: Arquillian Issue Type: Bug Components: Extension - Warp Affects Versions: warp_1.0.0.Alpha7, warp_1.0.0.Beta1 Environment: Linux x64, ChromeDriver , PhantomJSDriver, Wildfly 8.0 & 8.2, Mojarra 2.8 & 2.11 Reporter: Pëtr Andreev Attachments: ARQ-1952-failure.log, ARQ-1952-success.log 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|https://github.com/adamfisk/LittleProxy] 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.