From: "J.H." <warthog9@kernel.org>
To: Drew Northup <drew.northup@maine.edu>
Cc: git@vger.kernel.org
Subject: Re: Web browser and Git wiki (kernel.org) not getting along....
Date: Sat, 01 Jan 2011 23:58:23 -0800 [thread overview]
Message-ID: <4D20301F.5050002@kernel.org> (raw)
In-Reply-To: <1293941768.30849.32.camel@drew-northup.unet.maine.edu>
On 01/01/2011 08:16 PM, Drew Northup wrote:
> Are any other Opera users getting this error when attempting to go to
> https://git.wiki.kernel.org ?
Known bug in Opera, the problem lies in how it handles wild card
certificates. It is claimed to be fixed in the next version by another
user who has pushed the issue with Opera.
> "Unable to complete secure transaction
>
> You tried to access the address
> https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools,
> which is currently unavailable. Please make sure that the web address
> (URL) is correctly spelled and punctuated, then try reloading the page.
>
> Secure connection: fatal error (112) from server.
>
> https://git.wiki.kernel.org/index.php/Interfaces,_frontends,_and_tools
>
> Transmission failure.
> ....."
>
> I'm trying to figure out of this is a pure Opera problem or just a
> RedHat problem (ugh). (I'm also pretty darn sure that the server is up,
> as it loads up just fine in Firefox.....)
Pure Opera, it works fine from every other browser.
> Unless lots of other people on the list are interested I don't see the
> point in splattering replies back to it until (unless?) something
> interesting comes up, so this may be a case when culling the CC list is
> ok...
- John 'Warthog9' Hawley
Chief Kernel.org Administrator
next prev parent reply other threads:[~2011-01-02 7:59 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-02 4:16 Web browser and Git wiki (kernel.org) not getting along Drew Northup
2011-01-02 7:58 ` J.H. [this message]
2011-01-05 1:05 ` Maaartin
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4D20301F.5050002@kernel.org \
--to=warthog9@kernel.org \
--cc=drew.northup@maine.edu \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).