This time there is no way to configure the servlet-protocol to use https to communicate with the server. Because the ArquillianServletRunner is deployed in the context of the current 'application under test' the communication will fail when the application is configured to only allow https request to the current context. In my case (using glassfish), the request will return an 302 for an http request that is not handled by the ServletMethodExecutor (throwing IllegalStateException).

It would be nice when the protocol can be configured to use https for the communication. Another (not so nice) solution can be to follow the address from the Location Header after an 302 response (at least one time).

Workaround:
Disable forcing SSL communication for the test deployment, by using an adjusted web.xml.