- From: elf Pavlik <perpetual-tripper@wwelves.org>
- Date: Tue, 06 Mar 2012 10:18:36 +0000
- To: Henry Story <henry.story@bblfish.net>
- Cc: public-webid <public-webid@w3.org>
Excerpts from Henry Story's message of 2012-03-06 09:53:27 +0000: > > On 5 Mar 2012, at 11:46, elf Pavlik wrote: > > > > > trying https connections to domains of people your website states that you know: > > https://bblfish.net/ - (exception - common name www.foafssl.org) issuer: StartCom Ltd. > > That is because I don't yet have an https WebID, and I never claimed I did. You can't just > take an http url, s/http/https/ and get a valid URL; unless you find me making an owl:sameAs > claim. i haven't said that you've claimed https webid yet ;) and i get your point here! > > The https port on that machine is foafssl.org. > > I am building a 100% https web server, which will then give me an https WebID. i've tried to switch all my websites to HTTPS and start always using https:// when linking to them, but than having only single IP on the VPS which a friend made available to me, i've realized that some people who may like to see those sites still use windows xp, which has problems with SNI, as well as some other platform/browser combinations [1] if you or anyone here have by any chance some tips on how to deal with this limitation i would appreciate any pointers! [1] https://en.wikipedia.org/wiki/Server_Name_Indication#No_support =) ~ elf pavlik ~
Received on Tuesday, 6 March 2012 10:19:09 UTC