Re: Local web server

-public-webcrypto@w3.org
+public-test-infra@w3.org

Hi Jim,

Jim Schaad <ietf@augustcellars.com>, 2016-03-25 20:50 -0700:
> 
> The good news is I got the thing up and running.

Very glad to hear it

> The bad news is how many different things that I had go wrong and the
> various ways that they went wrong in the process.

Sorry—there’s definitely always some trial-and-error involved in getting it
all running and getting oriented. It would be great to get some of the docs
refined based on the problems you ran into. So I hope we can take time to
try do that.

> 1.  I am a windows people and unix shell scripts don't work on unix so
> they generally just get ignored.  The apparent command line that is
> needed to get it running is "py serve" which then will link through all
> of the different things to get running correctly.

OK, that’s important to have documented. I’m not sure who else from the
among the main group of reviewers have ever tried to run the system on
Windows, so your help with getting it documented would be much appreciated.

> 2.  Need to update the documents to state that git needs to be in the
> command path otherwise it silently goes boom when trying to build the
> manifest file.

Yeah. Rightly though, nothing should ever silently fail, so we should
actually also update the code to emit some error message for this case.

> 3.  Found another bug where I had the source pointing to
> "../resources/testharness.js" which crashed the manifest builder and this
> silently failed when it went boom.

Same comment as above :)

> 4. What do I need to put into my html files to make them run using https
> rather than http?  There is a requirement that they be run from a secure
> origin and http://web-platform.test is not considered to be one by chrome
> (quite rightly).

When you start the server it listens for https protocol request on port
8443 by default. So if you navigate to https://web-platform.test:8443/ you
can run the tests from there. As long as you already have the cert in your
trust store.

> 5.  I am not sure that I am happy with the idea of having to put the self
> signed certificate into my trust store, but that seems to be necessary.

Yes it is. Though in the case of Firefox the system can do some magic to
add it a way that doesn’t require you to do it manually.

> Is there any thought to getting a certificate that is trusted by some
> root that is already going to be in my root store?

No, not as far as I know, as Ryan Sleevi alludes to in his reply at
https://lists.w3.org/Archives/Public/public-webcrypto/2016Mar/0069.html
there’s no way an actual CA could issue a cert for web-platform.test.

Before we added support for running the tests from a secure origin, we had
a lot of discussion about if/how best to handle the cert, and what we have
now is what we resolved to go with (well, more than anything, James Graham
looked at the requirements and made it happen).

  —Mike

-- 
Michael[tm] Smith https://people.w3.org/mike