[ https://issues.jboss.org/browse/ARQ-1370?page=com.atlassian.jira.plugin.s... ] Lukáš Fryč commented on ARQ-1370: --------------------------------- There are two concerns we had to verify: * CommandService need to communicate with server no matter what is server's sevlets/filter configuration * proxy need to be able to handle HTTPS requests (as you reported it should be able already) * client needs to use HTTPS (I'n not sure whether the communication does not currently look like: {code} client --HTTP--> proxy --HTTPS with flag--> server {code} (so that proxy actually handles SSL handshake, overtaking the responsibility from the client) ---- I would try to run and modify CommandService tests [1] (TestClientToContainerChannel, TestContainerToClientChannel) to pass on the container configured as you have described: https://github.com/arquillian/arquillian-extension-warp/tree/master/ftest... There is a service we are testing: [https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/...] which communicates through bus: [https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/...] as you can see, we are using [HttpURLConnection|https://github.com/arquillian/arquillian-extension-warp/blob/master/impl/src/main/java/org/jboss/arquillian/warp/impl/client/commandBus/CommandBusOnClient.java#L183] to establish a connection to [WarpFilter|https://github.com/arquillian/arquillian-extension-warp/blob/m...] which can handle the CommandService request (it delegates the request to a [CommandBusOnServer|https://github.com/arquillian/arquillian-extension-war...]. -- 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