[arquillian-issues] [JBoss JIRA] (ARQ-1952) Warp requests hit the application port instead of LittleProxy`s one
Aslak Knutsen (JIRA)
issues at jboss.org
Thu May 21 12:04:19 EDT 2015
[ https://issues.jboss.org/browse/ARQ-1952?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13070112#comment-13070112 ]
Aslak Knutsen commented on ARQ-1952:
------------------------------------
Wondering if this feature would be helpful in this case; https://github.com/aslakknutsen/arquillian-core/commit/9a1ec4bc1d1f5c817675be4293aff38c6116cb06
> 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.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
More information about the arquillian-issues
mailing list