From: Peter Korsgaard <peter@korsgaard.com>
To: buildroot@busybox.net
Subject: [Buildroot] "The owner of buildroot.uclibc.org has configured their website improperly."
Date: Tue, 23 Feb 2016 22:14:27 +0100 [thread overview]
Message-ID: <87bn776sek.fsf@dell.be.48ers.dk> (raw)
In-Reply-To: <56CCC524.8020709@mind.be> (Arnout Vandecappelle's message of "Tue, 23 Feb 2016 21:46:28 +0100")
>>>>> "Arnout" == Arnout Vandecappelle <arnout@mind.be> writes:
Hi,
>> Secondly, the reason why you get this error is that the uClibc
>> developers have recently added HSTS for *.uclibc.org (which forces
>> https:// access), and the certificate we use for Buildroot doesn't list
>> the legacy buildroot.uclibc.org address.
> The fix could be that the webserver is configured to redirect
> buildroot.uclibc.org to buildroot.org, instead of serving it directly.
It does send a redirect when you use http, but because of the HSTS with
subdomains on uclibc.org the browser ends up requesting
https://buildroot.uclibc.org which currently is an alias for
https://buildroot.org, so it serves the page with a non matching
certificate.
Even if change it so https://buildroot.uclibc.org serves a redirect we
still need to respond with a valid certificate, so I'll try to fix that
with letsencrypt.
--
Venlig hilsen,
Peter Korsgaard
next prev parent reply other threads:[~2016-02-23 21:14 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-23 16:59 [Buildroot] "The owner of buildroot.uclibc.org has configured their website improperly." Patrick Doyle
2016-02-23 20:34 ` Peter Korsgaard
2016-02-23 20:46 ` Arnout Vandecappelle
2016-02-23 21:14 ` Peter Korsgaard [this message]
2016-02-24 15:41 ` Peter Korsgaard
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=87bn776sek.fsf@dell.be.48ers.dk \
--to=peter@korsgaard.com \
--cc=buildroot@busybox.net \
/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