[jira] [Commented] (JCR-4574) add tests for https

["Konrad Windszus (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/JCR-4574?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17151989#comment-17151989 ] 

Konrad Windszus commented on JCR-4574:
--------------------------------------

Currently all tests in https://github.com/apache/jackrabbit/blob/0f0807d25283b8786d800dcc41821443f43c2f82/jackrabbit-spi2dav/pom.xml#L41 are disabled and enabling those leads to errors like 
{code}
[ERROR] testPathValueGetPath(org.apache.jackrabbit.spi.QValueTest)  Time elapsed: 0.001 s  <<< ERROR!
javax.jcr.RepositoryException: Connect to localhost:8080 [localhost/127.0.0.1, localhost/0:0:0:0:0:0:0:1] failed: Connection refused (Connection refused)
	at org.apache.jackrabbit.spi.QValueTest.setUp(QValueTest.java:49)
{code}

It seems that currently the server is not automatically started.
[~reschke] Do you have some hints on how to start Jackrabbit for the ITs?

> add tests for https
> -------------------
>
>                 Key: JCR-4574
>                 URL: https://issues.apache.org/jira/browse/JCR-4574
>             Project: Jackrabbit Content Repository
>          Issue Type: Task
>          Components: jackrabbit-jcr-server
>            Reporter: Julian Reschke
>            Priority: Minor
>         Attachments: https.diff
>
>
> With JCR-4169 done, it would be good if we could start testing with https as well.
> The first step would be to verify that - if the server runs with an incorrect or self-signed certificate - the client will indeed refuse to connect.
> That would be a precondition before adding knobs to relax the cert checking, as proposed in JCR-4536-



--
This message was sent by Atlassian Jira
(v8.3.4#803005)