[
https://issues.jboss.org/browse/ARQ-992?page=com.atlassian.jira.plugin.sy...
]
Lukáš Fryč commented on ARQ-992:
--------------------------------
I think the resolution pretty much reflects the "client-side filtering" idea
(ARQ-967).
You would install the filter {{REDIRECTED_REQUEST}},
this just makes the "client-side filtering" statefull, depending on state of
previous request.
It would also mean that client needs to be provided with information the request is going
to be redirected
----
We could certainly use automatic redirection handling on proxy, but it might be perceived
as "magic".
Warp does not support request redirection.
------------------------------------------
Key: ARQ-992
URL:
https://issues.jboss.org/browse/ARQ-992
Project: Arquillian
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Extension - Warp
Affects Versions: warp_1.0.0.Alpha1
Environment: JBoss AS 7.1.1
Reporter: Jakub Narloch
Assignee: Lukáš Fryč
Labels: warp
When I was running tests of Spring controllers I found out that whenever a controller is
redirecting the response for example by returning a String as view name: {code}return
"redirect:welcome.do"{code} the execution of the test hangs till end of
timeout.
I've debuged the WarpFilter and it seems that the Warp header is not beeing added
into the 302 HTTP response. On the client side this result with ResponseDeenrichmentFilter
can not find any ResponsePayload in response.
Taking into consideration fact that the RequestEnrichmentFilter allows to push the
assertion only once, so when the second request is being made the assertion is not being
send once again I'm unable to test such response.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira