Roel Janssen skribis:
> It looks like we've got that CORS problem again.
What makes you say so?
> Did you change the web server configuration at hydra.gnu.org?
Starting from a few hours ago, nginx at hydra.gnu.org times out after
~10s instead of 60s. So when hydra.gnu.org is loaded, the /api
It looks like we've got that CORS problem again.
Did you change the web server configuration at hydra.gnu.org?
Kind regards,
Roel
Ludovic Courtès (2016-03-19 00:08 +0300) wrote:
> Alex Kost skribis:
>
>> Roel Janssen (2016-03-18 00:53 +0300) wrote:
>>
>>> Ludovic Courtès writes:
>> [...]
Starting from a few hours ago, nginx at hydra.gnu.org times out after
~10s instead of 60s. So when hydra.gnu.org is loaded, the
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> It looks like we've got that CORS problem again.
>
> What makes you say so?
The "web console" in Firefox reported so. However, I cannot reproduce
that anymore. :)
>> Did you change the web server configuration at hydra.gnu.org?
>
> Starting
Alex Kost skribis:
> Roel Janssen (2016-03-18 00:53 +0300) wrote:
>
>> Ludovic Courtès writes:
> [...]
>>> Starting from a few hours ago, nginx at hydra.gnu.org times out after
>>> ~10s instead of 60s. So when hydra.gnu.org is loaded, the /api requests
>>> time out and we don’t get build status
Roel Janssen skribis:
> Ludovic Courtès writes:
>> Starting from a few hours ago, nginx at hydra.gnu.org times out after
>> ~10s instead of 60s. So when hydra.gnu.org is loaded, the /api requests
>> time out and we don’t get build status icons.
>
> Well, 10 seconds is a lot of time.
I used a s
Roel Janssen (2016-03-18 00:53 +0300) wrote:
> Ludovic Courtès writes:
[...]
>> Starting from a few hours ago, nginx at hydra.gnu.org times out after
>> ~10s instead of 60s. So when hydra.gnu.org is loaded, the /api requests
>> time out and we don’t get build status icons.
>
> Well, 10 seconds is
On Tue, Mar 15, 2016 at 11:01:27PM +0100, Ludovic Courtès wrote:
> Roel Janssen skribis:
>
> > From 28cfe3d56d2139fc4a50ac9b20b2a73fe12f5a6c Mon Sep 17 00:00:00 2001
> > From: Roel Janssen
> > Date: Tue, 15 Mar 2016 22:45:32 +0100
> > Subject: [PATCH] website: packages: Support both http and htt
Ludovic Courtès writes:
> Roel Janssen skribis:
>
>> From 28cfe3d56d2139fc4a50ac9b20b2a73fe12f5a6c Mon Sep 17 00:00:00 2001
>> From: Roel Janssen
>> Date: Tue, 15 Mar 2016 22:45:32 +0100
>> Subject: [PATCH] website: packages: Support both http and https requests to
>> hydra.gnu.org.
>>
>> * we
Roel Janssen skribis:
> From 28cfe3d56d2139fc4a50ac9b20b2a73fe12f5a6c Mon Sep 17 00:00:00 2001
> From: Roel Janssen
> Date: Tue, 15 Mar 2016 22:45:32 +0100
> Subject: [PATCH] website: packages: Support both http and https requests to
> hydra.gnu.org.
>
> * website/static/base/js/packages.js (se
>From 28cfe3d56d2139fc4a50ac9b20b2a73fe12f5a6c Mon Sep 17 00:00:00 2001
From: Roel Janssen
Date: Tue, 15 Mar 2016 22:45:32 +0100
Subject: [PATCH] website: packages: Support both http and https requests to
hydra.gnu.org.
* website/static/base/js/packages.js (set_build_status): Use the protocol of
Hello!
It took a while, but finally hydra.gnu.org has its own Let’s Encrypt
certificate and is available over https, woohoo!
Back to the initial problem, we (i.e., you ;-)) can now modify
packages.js so that it uses either http or https to use Hydra’s API,
depending on the current URL.
Thoughts?
On Thu, Feb 04, 2016 at 11:56:52PM +0100, Roel Janssen wrote:
> Dear list,
>
> I would like to propose adding HTTPS support for hydra.gnu.org. The
> direct need to have this set up, is to allow the build status icons to
> load on the packages page of the Guix website.
>
> Fortunately, this shoul
13 matches
Mail list logo