Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Uses https for non SSL links #247

Closed
michael-n-cooper opened this issue Jul 26, 2013 · 3 comments
Closed

Uses https for non SSL links #247

michael-n-cooper opened this issue Jul 26, 2013 · 3 comments

Comments

@michael-n-cooper
Copy link
Member

Using the "Save as XHTML 5 (Source)" with Firefox 19, observed most recently on https://dvcs.w3.org/hg/IndieUI/raw-file/tip/src/indie-ui-events.html but have seen on other Respec-based documents as well.

The link to the required CSS for W3C specs, and the source for the W3C logo, are output with an https URI, but these are non-SSL resources and should be http URIs. For instance the style link for a Working Draft comes out as https://www.w3.org/StyleSheets/TR/W3C-WD, but it should be http://www.w3.org/StyleSheets/TR/W3C-WD; the icon source is https://www.w3.org/Icons/w3c_home when it should be http://www.w3.org/Icons/w3c_home. This causes some Pubrules checks to fail.

@marcoscaceres
Copy link
Member

XHTML is deprecated, no? Is there any reason why you are using it?

@michael-n-cooper
Copy link
Member Author

I really hope this issue doesn't start a new existential debate about the value of XHTML, nor would I expect the fact that I used XHTML to be behind this particular issue. Whether Respec should support XHTML was debated at http://lists.w3.org/Archives/Public/spec-prod/2013JanMar/thread.html#msg13; I gave my own views at http://lists.w3.org/Archives/Public/spec-prod/2013JanMar/0014.html; and since Respec continues to support it I prefer to use it. It would introduce other problems for me to remove that support, but that is a different issue than the one I filed here.

@darobin
Copy link
Member

darobin commented Aug 5, 2013

That's not an XHTML-related problem anyway. That said, if this causes pubrules problems then it's a bug in pubrules. We tried being smart about which scheme to use here, but the only option that produces no problems is to enforce https.

So this requires a fix in pubrules (I thought it had been fixed already, but maybe not completely).

Unrelated but: Firefox 19 is a bit out of date!

@darobin darobin closed this as completed Aug 5, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants