On Tue, Sep 9, 2008 at 3:24 PM, Ilmari Karonen <nospam(a)vyznev.net> wrote:
Gregory Maxwell wrote:
On this subject, as part of the IPv6 testing I've run a JS tester on
ENWP for a couple of months now which has determined that for hosts
able to run the JS tester, protocol relative urls (i.e. <img
src="//upload.wikimedia.org/foo.jpg"/>) work for all clients.
If protocol relatives turn out to be universally supported they would
remove one problem from doing a native SSL deployment.
I can't comment on compatibility with clients that do not support
javascript / don't execute the v6 test for some other reason.
So, could we/you just add a couple of small images to some unobtrusive
place in the MonoBook skin on enwiki, with one using a protocol-relative
URL and the other not, and see what happens?
I've basically done this. Not in the monobook skin, but injected via
JS for 1:100 requests along with the IPv6 test. The unambiguous result
is that it works.
The open question is: "does it work for more primitive clients which
do not support JS?" We could use non-JS images, but we'd have no way
to get error reports.
The only further test I could really see doing would be doing
something like using them for all images and seeing if people start
reporting "Wikipedia has no images anymore on my cell phone!", but
caching means that if it does cause problems we can't instantly
revert.
Good ideas welcome.