CNAMEs in bitbucket

[Alan Mackenzie]

Hello, XEmacs.

A little while ago, whilst committing a change to the CC Mode part of
xemacs-packages at bitbucket, I was alerted by a message (which I didn't
save) saying that as from 2015-07-01, CNAMEs (something to do with URLs)
will be disabled, and that some scripts, and what not, may need amending
consequently.

Is this already known to the XEmacs team? Does anything need to be
done?

[Stephen J. Turnbull]

Post by Alan Mackenzie
A little while ago, whilst committing a change to the CC Mode part of
xemacs-packages at bitbucket, I was alerted by a message (which I didn't
save) saying that as from 2015-07-01, CNAMEs (something to do with URLs)
will be disabled, and that some scripts, and what not, may need amending
consequently.

Thanks for the report.

Post by Alan Mackenzie
Is this already known to the XEmacs team? Does anything need to be
done?

I already know about it. I don't think anything actually needs to be
done by the XEmacs team except fix some READMEs. AIUI, they can't
actually disable CNAMEs for SSH users, since the SSH protocol doesn't
tell the server the originating domain, only the IP. What they are
doing is disabling support for use of CNAMEs in the HTTPS URL.

This is an annoyance for HTTPS users who have used the CNAME in the
past, but we can't do anything about that. They have to fix their
.hg/hgrc for themselves.