Am 02/23/2015 11:10 AM, schrieb Michal Hri:
Dňa nedeľa, 22. február 2015 22:10 ,Andrea Pescetti
napísal:
Marcus wrote:
now the main and download webpage will be loaded via HTTPS only.
Thanks Marcus, I confirm that https://www.openoffice.org now doesn't
give either the "HTTP components" warni
Dňa nedeľa, 22. február 2015 22:10 ,Andrea Pescetti
napísal:
Marcus wrote:
> now the main and download webpage will be loaded via HTTPS only.
Thanks Marcus, I confirm that https://www.openoffice.org now doesn't
give either the "HTTP components" warning or the "identity information"
warning
Marcus wrote:
now the main and download webpage will be loaded via HTTPS only.
Thanks Marcus, I confirm that https://www.openoffice.org now doesn't
give either the "HTTP components" warning or the "identity information"
warning any longer. So everything works for me with HTTPS.
Of course, h
Am 02/20/2015 08:30 PM, schrieb Marcus:
Am 02/20/2015 08:07 PM, schrieb Marcus:
I've started with the download webpage as I know it very well. I don't
see any errors as it looks like before.
But I'll leave it for the moment and go on earliest on Sunday.
now the main and download webpage will
Am 02/20/2015 08:07 PM, schrieb Marcus:
I've started with the download webpage as I know it very well. I don't
see any errors as it looks like before.
But I'll leave it for the moment and go on earliest on Sunday.
grrr, some change was too much. So, I've reverted the changes for now
and will
I've started with the download webpage as I know it very well. I don't
see any errors as it looks like before.
But I'll leave it for the moment and go on earliest on Sunday.
Marcus
Am 02/19/2015 11:49 PM, schrieb Marcus:
Am 02/19/2015 11:14 PM, schrieb Andrea Pescetti:
On 19/02/2015 Marcus
On 20 February 2015 at 00:34, Dave Fisher wrote:
> Hi -
>
> We had a reason that we enabled https in the first place. I don't recall
> it now, but there was a reason. It may have had to do with update servers.
>
The main web server on which we run, have always been enabled for both
http: and http
Hi -
We had a reason that we enabled https in the first place. I don't recall it
now, but there was a reason. It may have had to do with update servers.
Regards,
Dave
On Feb 19, 2015, at 2:49 PM, Marcus wrote:
> Am 02/19/2015 11:14 PM, schrieb Andrea Pescetti:
>> On 19/02/2015 Marcus wrote:
>>
Am 02/19/2015 11:14 PM, schrieb Andrea Pescetti:
On 19/02/2015 Marcus wrote:
OK, next try. Still an error message?
Well... we NOWHERE, and I repeat NOWHERE, advertise the URL
https://www.openoffice.org ; as a courtesy to those people who prefer
HTTPS, we make it available, but if they use brok
Andrea Pescetti wrote on 19/02/15 23:14:
> On 19/02/2015 Marcus wrote:
>> OK, next try. Still an error message?
>
> Well... we NOWHERE, and I repeat NOWHERE, advertise the URL
> https://www.openoffice.org ; as a courtesy to those people who prefer
> HTTPS, we make it available, but if they use brok
On Thu, Feb 19, 2015 at 5:33 PM, jan i wrote:
> On Thursday, February 19, 2015, Andrea Pescetti
> wrote:
>
> > On 19/02/2015 Marcus wrote:
> >
> >> OK, next try. Still an error message?
> >>
> >
> > Well... we NOWHERE, and I repeat NOWHERE, advertise the URL
> > https://www.openoffice.org ; as a
On Thursday, February 19, 2015, Andrea Pescetti wrote:
> On 19/02/2015 Marcus wrote:
>
>> OK, next try. Still an error message?
>>
>
> Well... we NOWHERE, and I repeat NOWHERE, advertise the URL
> https://www.openoffice.org ; as a courtesy to those people who prefer
> HTTPS, we make it available,
On 19/02/2015 Marcus wrote:
OK, next try. Still an error message?
Well... we NOWHERE, and I repeat NOWHERE, advertise the URL
https://www.openoffice.org ; as a courtesy to those people who prefer
HTTPS, we make it available, but if they use broken extensions or
paranoid security settings the
Am 02/19/2015 09:48 PM, schrieb Ariel Constenla-Haile:
On Thu, Feb 19, 2015 at 07:10:56PM +0100, Marcus wrote:
I've changed all links for the grey box from HTTP to HTTPS. Let's see if
this will help to solve the problem.
The correct solution is to use src="/path/to/image", not forcing the
prot
Am 02/19/2015 09:09 PM, schrieb Keith N. McKenna:
Marcus wrote:
Am 02/19/2015 08:08 PM, schrieb Keith N. McKenna:
Marcus wrote:
Am 02/19/2015 02:36 PM, schrieb jan i:
On 19 February 2015 at 14:14, Simon Phippswrote:
On Thu, Feb 19, 2015 at 6:26 AM, jan iwrote:
On Thursday, Februar
On Thu, Feb 19, 2015 at 07:10:56PM +0100, Marcus wrote:
> I've changed all links for the grey box from HTTP to HTTPS. Let's see if
> this will help to solve the problem.
The correct solution is to use src="/path/to/image", not forcing the
protocol on the url.
Regards
--
Ariel Constenla-Haile
La
Marcus wrote:
> Am 02/19/2015 08:08 PM, schrieb Keith N. McKenna:
>> Marcus wrote:
>>> Am 02/19/2015 02:36 PM, schrieb jan i:
On 19 February 2015 at 14:14, Simon Phipps wrote:
> On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
>>
>> On Thursday, February 19, 2015, Dennis E. H
Am 02/19/2015 08:08 PM, schrieb Keith N. McKenna:
Marcus wrote:
Am 02/19/2015 02:36 PM, schrieb jan i:
On 19 February 2015 at 14:14, Simon Phipps wrote:
On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
On Thursday, February 19, 2015, Dennis E. Hamilton<
dennis.hamil...@acm.org>
wrote:
Marcus wrote:
> Am 02/19/2015 02:36 PM, schrieb jan i:
>> On 19 February 2015 at 14:14, Simon Phipps wrote:
>>
>>> On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
On Thursday, February 19, 2015, Dennis E. Hamilton<
>>> dennis.hamil...@acm.org>
wrote:
> "The connectio
Am 02/19/2015 02:36 PM, schrieb jan i:
On 19 February 2015 at 14:14, Simon Phipps wrote:
On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
On Thursday, February 19, 2015, Dennis E. Hamilton<
dennis.hamil...@acm.org>
wrote:
"The connection to this web site is not fully secure
On Thu, Feb 19, 2015 at 6:01 PM, jan i wrote:
> On Thursday, February 19, 2015, Keith N. McKenna <
> keith.mcke...@comcast.net>
> wrote:
>
> > jan i wrote:
> > > On 19 February 2015 at 14:14, Simon Phipps > > wrote:
> > >
> > >> On Thu, Feb 19, 2015 at 6:26 AM, jan i >
> > wrote:
> > >>>
> > >>
On Thursday, February 19, 2015, Keith N. McKenna
wrote:
> jan i wrote:
> > On 19 February 2015 at 14:14, Simon Phipps > wrote:
> >
> >> On Thu, Feb 19, 2015 at 6:26 AM, jan i >
> wrote:
> >>>
> >>> On Thursday, February 19, 2015, Dennis E. Hamilton <
> >> dennis.hamil...@acm.org >
> >>> wrote:
>
jan i wrote:
> On 19 February 2015 at 14:14, Simon Phipps wrote:
>
>> On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
>>>
>>> On Thursday, February 19, 2015, Dennis E. Hamilton <
>> dennis.hamil...@acm.org>
>>> wrote:
>>>
"The connection to this web site is not fully secure
I tried it on 2 different computers and both got the error.
Brenda
From: jan i
Sent: Thursday, February 19, 2015 1:26 AM
To: dev@openoffice.apache.org ; dennis.hamil...@acm.org
Cc: blissfulh...@live.com
Subject: Re: website security certificate
On Thursday, February 19, 2015, Dennis E
On 19 February 2015 at 14:14, Simon Phipps wrote:
> On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
> >
> > On Thursday, February 19, 2015, Dennis E. Hamilton <
> dennis.hamil...@acm.org>
> > wrote:
> >
> > >"The connection to this web site is not fully secure
> > >because it conta
On Thu, Feb 19, 2015 at 6:26 AM, jan i wrote:
>
> On Thursday, February 19, 2015, Dennis E. Hamilton <
dennis.hamil...@acm.org>
> wrote:
>
> >"The connection to this web site is not fully secure
> >because it contains unencrypted elements (such as
> >images)."
Perhaps the
update
it.
-- the certificate was changed some 5-6 month ago, due to a security fix.
rgds
jan i
in any way
>
> - Dennis
>
>
>
> -Original Message-
> From: Brenda [blissfulh...@live.com ]
> Sent: Wednesday, February 18, 2015 13:07
> To: dennis.hamil...@acm.org
>
u would see that is relevant in the
.jpg, so I won't bother to upload it.
- Dennis
-Original Message-
From: Brenda [blissfulh...@live.com]
Sent: Wednesday, February 18, 2015 13:07
To: dennis.hamil...@acm.org
Subject: Re: website security certificate
It said something like the securit
o:brendaleewilk...@hotmail.com]
Sent: Wednesday, February 18, 2015 07:28
To: dev@openoffice.apache.org
Subject: website security certificate
When I was trying to go onto your website from a google search is said their
was an issue with your security certificate and recommended not continui
When I was trying to go onto your website from a google search is said their
was an issue with your security certificate and recommended not continuing to
the site. Thought I'd let you know in case it's killing your traffic.
Brenda
30 matches
Mail list logo
