[JBoss JIRA] (ARQ-1286) Support Warp on Java EE 5 (Servlets 2.5) compliant containers
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1286?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1286:
----------------------------
Complexity: Low
> Support Warp on Java EE 5 (Servlets 2.5) compliant containers
> -------------------------------------------------------------
>
> Key: ARQ-1286
> URL: https://issues.jboss.org/browse/ARQ-1286
> Project: Arquillian
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Reporter: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Original Estimate: 4 hours
> Remaining Estimate: 4 hours
>
> Warp is currently focused on Java EE 6 and higher, since it uses {{@WebFilter}} annotation to intercept incoming requests.
> We may decide to support Servlets 2.5 containers as well in case there is enough interest (please vote if you are interested).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1325) Warp: replace piggy-backing on request/response with direct test->filter communication
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1325?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1325:
----------------------------
Sprint: Critical Issues
> Warp: replace piggy-backing on request/response with direct test->filter communication
> --------------------------------------------------------------------------------------
>
> Key: ARQ-1325
> URL: https://issues.jboss.org/browse/ARQ-1325
> Project: Arquillian
> Issue Type: Enhancement
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Reporter: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> We can do similar processing as we did with CommandService here:
> https://github.com/arquillian/arquillian-extension-warp/blob/aa0745237f5d...
> The CommandService communicates with the WarpFilter asynchronously and its requests are not processed directly, they delegates to the request-serving routine.
> ----
> This way, Warp could:
> 0. request is issued against proxy
> 1. catch the request on the proxy
> 2. register the RequestPayload (with Inspection) in the registry via the WarpFilter (under generated request-specific UUID)
> 3. proxy passes request to WarpFilter with a request header which contains UUID
> 4. WarpFilter associates Inspection from the registry with given request
> 5. Warp proceeds with a request inspection
> 6. response is commited and sent back to the proxy (with given UUID as response header)
> 7. proxy catches the response and obtains ResponsePayload (with Inspection result) from the WarpFilter (using UUID)
> 8. proxy processes the ResponsePayload and passes the request to the client
> 9. the client processes response
> This would avoid a need for piggy-backing on request/response, so it will also eliminate need for response-wrapping (NonWritingResponse).
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months
[JBoss JIRA] (ARQ-1324) Warp HTTP request header size beyond reasonable limits
by Lukáš Fryč (JIRA)
[ https://issues.jboss.org/browse/ARQ-1324?page=com.atlassian.jira.plugin.s... ]
Lukáš Fryč updated ARQ-1324:
----------------------------
Sprint: Critical Issues
> Warp HTTP request header size beyond reasonable limits
> ------------------------------------------------------
>
> Key: ARQ-1324
> URL: https://issues.jboss.org/browse/ARQ-1324
> Project: Arquillian
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: Extension - Warp
> Affects Versions: warp_1.0.0.Alpha2
> Environment: JBoss AS 7.1.1.Final
> Reporter: Marek Schmidt
> Assignee: Lukáš Fryč
> Priority: Critical
> Fix For: warp_1.0.0.Beta1
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> HTTP servers usually limit HTTP header size of the requests (e.g. 8192 bytes for AS7) and refuse to accept requests with larger headers with "Invalid request" errors. Such limit is easily exceeded by a non-trivial Inspection object.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
11 years, 10 months