maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Paul Benedict (JIRA)" <j...@codehaus.org>
Subject [jira] (MNG-3230) HTTPS with self-signed certificate does not work, no error message.
Date Wed, 02 Jul 2014 13:44:44 GMT

     [ https://jira.codehaus.org/browse/MNG-3230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Paul Benedict updated MNG-3230:
-------------------------------

    Fix Version/s:     (was: Issues to be reviewed for 3.x)

> HTTPS with self-signed certificate does not work, no error message.
> -------------------------------------------------------------------
>
>                 Key: MNG-3230
>                 URL: https://jira.codehaus.org/browse/MNG-3230
>             Project: Maven
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>    Affects Versions: 2.0.7
>            Reporter: Andreas Kr├╝ger
>
> We have a repository server that serves the same files both via HTTPS and HTTP.
> Maven is not able to find artifacts when using HTTPS. All goes well when using HTTP.
> The problem probably is that the HTTPS - certificate used by the repository server is
self-signed, and Maven has not been configured to accept that certificate as genuine. (This
is a guess.)
> Expected behavior: With HTTPS, build does not continue. Maven gives an error message
indicating the problem is certificate-related.
> Behavior seen: Maven reacts as if there were no problem connecting the repository, but
as if the artifact were missing from the repository. It continues to search other repositories
as happen to be configured. (However, the artifact is clearly there, e.g., can be downloaded
with "wget  --no-check-certificate " via HTTPS.)



--
This message was sent by Atlassian JIRA
(v6.1.6#6162)

Mime
View raw message