Re: Can an upate center be on a site that requires https?

Sean Phillips <[email protected]>
Newsgroups gmane.comp.java.netbeans.modules.openide.devel
Message-ID <CAHFxjTiHBo_W-oT+xAeZNh0_jUa_hJLpNRbg3Ag1oBki=d_FxQ@mail.gmail.com>
I can confirm this with my own findings.
I was able to serve out an Update Center using an HTTPS Subversion
repository even.  This was super convenient because the platform will
automatically popup a username/password dialog when attempting to connect
to such an Update center.
I love the platform.
Sean

On Tue, Dec 1, 2015 at 11:34 AM, Peter Hansson <[email protected]>
wrote:

> There's no problem. It can be HTTPS as well as HTTP.
>
> The only thing you have to remember - and this is not documented - is that
> verification of the server's certificate has been turned off in the NB
> Platform code. Any server certificate will be accepted.
> Why this is so I don't know. I suspect it was handy when the code was
> developed and then it was not removed when the code went into production.
>
> Peter
>
> On Mon, Nov 30, 2015 at 11:20 PM, jhuber <[email protected]> wrote:
>
>> Hello!
>>
>> The examples and docs I've found for setting up an update center have all
>> used a regular http URL, such as
>> Code:
>> http://my_site.com/updates.xml
>>
>> .
>>
>> Can the update center be on a site that requires https, such as the
>> update center link would be
>> Code:
>> https://my_site.com/updates.xml
>>
>> ?
>>
>> Perhaps the https negotiation all happens in the background and NetBeans
>> doesn't care???
>>
>> Thanks!
>>
>>
>>
>>
>>
>
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.