You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2020/07/03 16:04:00 UTC

[jira] [Commented] (JCR-4536) Feature/enable insecure https host

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

Konrad Windszus commented on JCR-4536:
--------------------------------------

As I also recently stumbled upon this let me try to pick this up.

[~reschke] Related to your questions

bq. Why is this needed now? Wouldn't it be better to have the development server have a correct cert, from instance from LE?

Indeed, but certain setups (i.e. Adobe Managed Services) do not provide a proper certificate for their endpoints

I will try to rework the patch a bit to have less changes in it.  

> Feature/enable insecure https host
> ----------------------------------
>
>                 Key: JCR-4536
>                 URL: https://issues.apache.org/jira/browse/JCR-4536
>             Project: Jackrabbit Content Repository
>          Issue Type: Improvement
>          Components: jackrabbit-spi2dav
>            Reporter: Max Barrass
>            Priority: Major
>
> Adding support for insecure parameter to allow access to https with invalid certs.
> Enabling optional support for expired ssl certs when using https on development server with self generated certificates.
> Pull request already created and ready for review [https://github.com/apache/jackrabbit/pull/88]



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