Re: Stability of HTTPS for w3c-test.org

Yes, CR testing is one of the use cases. Also, quickly checking failures,
referencing tests in bug reports, and running tests on devices where a
local server is not possible.

Can anyone speak to the issue with HTTPS connections on the server? HTTPS
connections seem to timeout as much as they succeed, and they can be
unavailable for an hour or more at a time.

Shane McCarron <shane@spec-ops.io> wrote:

> I agree with James, unless you are doing actual CR testing and you want to
> run against the canonical source for some reason anyway.
>
> On Wed, Oct 5, 2016 at 1:53 PM, James Graham <james@hoppipolla.co.uk <james@hoppipolla.co.uk?Subject=Re%3A%20Stability%20of%20HTTPS%20for%20w3c-test.org&In-Reply-To=%3CCAJdbnOB%2Bsv7PweAVyP60__%3Dsr7vnarCYgh3XBLcSey53qzfT2A%40mail.gmail.com%3E&References=%3CCAJdbnOB%2Bsv7PweAVyP60__%3Dsr7vnarCYgh3XBLcSey53qzfT2A%40mail.gmail.com%3E>> wrote:
>
> > On 05/10/16 19:45, David Dorwin wrote:
> >
> > Is the stability on HTTPS a known issue? Are there plans to address it?
> >> With tests being written using features that require HTTPS, it's
> >> important that https://w3c-test.org be reliable.
> >>
> >
> > ithout commenting on the wider issue, I think you should regard
> > w3c-test.org as a convenience service rather than an essential part of
> > your workflow. For any serious work I recommend spinning up the server
> > locally (edit your hosts file and run ./serve in the web-platform-tests
> > checkout).
> >
> >
> >
>
>
> --
> Shane McCarron
> Projects Manager, Spec-Ops
>
>