Why is HTTPS not supported? It's supported by the engine and by at least BibleTime and Xiphos AFAIK.
--Greg On Tue, Sep 1, 2015 at 9:03 PM, Kahunapule Michael Johnson < kahunap...@ebible.org> wrote: > The main repository has been updated with revised modules with Strong's > numbers (5 of them). The update is about markup and conf files, with no > change to source text. > > Also, I used symbolic links to allow the /pub in the directory to be > omitted. In other words, ftp://ftp.eBible.org/sword works just as well as > ftp://ftp.eBible.org/pub/sword and ftp://ftp.eBible.org/swordbeta works > just as well as ftp://ftp.eBible.org/pub/swordbeta. > > If you ever wonder if you are getting the latest version and suspect > ISP-level caching of defeating my updates, you can try using > https://eBible.org/sword/. The HTTPS protocol isn't currently a supported > repository access method, but you could use a browser to grab a copy of > what you are interested in, then install locally from that copy. > -- > Your partner in electronic Bible publishing, > > > > *MICHAEL JOHNSON PO BOX 881143 PUKALANI HI 96788-1143* > USA eBible.org > MLJohnson.org > Mobile: +1 *808-333-6921 <808-333-6921>* > Skype: kahunapule > > _______________________________________________ > sword-devel mailing list: sword-devel@crosswire.org > http://www.crosswire.org/mailman/listinfo/sword-devel > Instructions to unsubscribe/change your settings at above page >
_______________________________________________ sword-devel mailing list: sword-devel@crosswire.org http://www.crosswire.org/mailman/listinfo/sword-devel Instructions to unsubscribe/change your settings at above page
