W3C home > Mailing lists > Public > spec-prod@w3.org > July to September 2013

Re: ReSpec and https

From: Ian Jacobs <ij@w3.org>
Date: Wed, 14 Aug 2013 16:18:56 -0500
Cc: "Tab Atkins Jr." <jackalmage@gmail.com>, Tim Bray <tbray@textuality.com>, Shane McCarron <shane@aptest.com>, Robin Berjon <robin@w3.org>, "spec-prod@w3.org Prod" <spec-prod@w3.org>, Dom Hazael-Massieux <dom@w3.org>, Jérémie Astori <jeremie@w3.org>
Message-Id: <6C8E3EBF-8436-4DDF-9F51-33850F66941A@w3.org>
To: "Markus Lanthaler" <markus.lanthaler@gmx.net>

On Aug 14, 2013, at 12:33 PM, "Markus Lanthaler" <markus.lanthaler@gmx.net> wrote:

> On Wednesday, August 14, 2013 7:20 PM, Ian Jacobs wrote:
>> On Aug 14, 2013, at 12:17 PM, "Tab Atkins Jr." <jackalmage@gmail.com>
>> wrote:
>> 
>>> On Wed, Aug 14, 2013 at 10:14 AM, Tim Bray <tbray@textuality.com> wrote:
>>>> And anyhow, couldn't you have respec generate relative URIs starting
> with
>>>> //w3.org/...?  That way they get whichever of http: or https: the
>> original page was fetched with.  -T
>>> 
>>> Not if you're doing local edits, and thus viewing it at a file: url,
>>> as Robin said.
>> 
>> That comes back to the point that perhaps in "editor's draft" mode
>> respec does one thing, then in "ready to publish" mode it does another.
> 
> As Robin already said. We tried a couple of things. All that smartness had
> negative side effects (just look at a copy in a Mercurial repo which is by
> default https) and using https by default doesn't have any AFAICT. So I
> would like to keep https for these two.

I've modified the checker. I think it should support https URIs for the W3C logo and TR styles.

Let me know if it works for you. If so, I'll mention on the chairs list as well.

Ian

--
Ian Jacobs <ij@w3.org>      http://www.w3.org/People/Jacobs
Tel:                                          +1 718 260 9447
Received on Wednesday, 14 August 2013 21:19:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 19:55:19 UTC