From: Roel Janssen <roel@gnu.org>
To: "Ludovic Courtès" <ludo@gnu.org>
Cc: guix-devel@gnu.org
Subject: Re: Cross-Origin Request blocked when browing non-www of packages page and mixed content
Date: Tue, 03 May 2016 13:30:10 +0200 [thread overview]
Message-ID: <87d1p35qgt.fsf@gnu.org> (raw)
In-Reply-To: <87inz315j8.fsf@gnu.org>
Ludovic Courtès writes:
> Hello!
>
> Roel Janssen <roel@gnu.org> skribis:
>
>> I noticed that the build status icons don't work when browing:
>> https://gnu.org/software/guix/packages/ (Notice the lack of 'www.')
>>
>> The reason:
>> CORS header 'Access-Control-Allow-Origin' does not match
>> 'https://www.gnu.org'.
>>
>> So, could we either add 'https://gnu.org' to the Hydra nginx config, or
>> add a redirect to the www-variant on gnu.org?
>
> I don’t know how to fix it: there can be only one CORS header and it
> can contain only one URL. Thoughts?
>
> Regarding www.gnu.org, it’s something to ask webmasters@gnu.org. Would
> you like to email them?
I e-mailed them.
>> Then, we also have the problem of loading mixed content (mixed transportation
>> over HTTP and HTTPS in the same page):
>
> I think it would be worth to try addressing this problem at the GNU
> scale, because this info (logo URLs, descriptions, etc.) is something we
> get from a canonical database of GNU packages; see (guix
> gnu-maintenance) for details.
>
> Could you email bug-womb@gnu.org with a suggestion to host all logos
> somewhere on gnu.org? I think it’d be beneficial not just for Guix.
For this I have to further look into it for the details. I don't have
time for that right now, but when I do find time, I'll have another
look.
Thanks for your time!
Kind regards,
Roel Janssen
next prev parent reply other threads:[~2016-05-03 11:31 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-04-20 8:29 Cross-Origin Request blocked when browing non-www of packages page and mixed content Roel Janssen
2016-04-27 14:37 ` Ludovic Courtès
2016-05-03 11:30 ` Roel Janssen [this message]
2016-05-16 19:30 ` Roel Janssen
2016-05-19 11:59 ` Ludovic Courtès
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=87d1p35qgt.fsf@gnu.org \
--to=roel@gnu.org \
--cc=guix-devel@gnu.org \
--cc=ludo@gnu.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.