Anecdata: just noting that our install of EG 2.12.5 on Ubuntu 16.04 seems to be working fine for us when relying on the indexdata yaz pacakges with our oils_z3950.xml stanzas connecting to HTTPS for SRU; it contains (for example):
<database name="LUSYS"> <zurl>https://www.concat.ca/opac/extras/sru/LUSYS/holdings</zurl> <option name="sru">get</option> <charset>UTF-8</charset> <search> <querytype>cql</querytype> <map use="4"><index>eg.title</index></map> <map use="7"><index>eg.isbn</index></map> <map use="8"><index>eg.issn</index></map> <map use="12"><index>eg.id</index></map> <map use="21"><index>eg.subject</index></map> <map use="1003"><index>eg.creator</index></map> <map use="1018"><index>eg.publisher</index></map> <map use="1035"><index>eg.keyword</index></map> <map use="1016"><index>eg.keyword</index></map> </search> </database>
# dpkg -s yaz Package: yaz Architecture: amd64 Version: 5.23.0-1.indexdata
Anecdata: just noting that our install of EG 2.12.5 on Ubuntu 16.04 seems to be working fine for us when relying on the indexdata yaz pacakges with our oils_z3950.xml stanzas connecting to HTTPS for SRU; it contains (for example):
<database name="LUSYS"> /www.concat. ca/opac/ extras/ sru/LUSYS/ holdings</zurl> >get</option> UTF-8</ charset>
<querytype> cql</querytype> ><index> eg.title< /index> </map> ><index> eg.isbn< /index> </map> ><index> eg.issn< /index> </map> ><index> eg.id</ index>< /map> ><index> eg.subject< /index> </map> ><index> eg.creator< /index> </map> ><index> eg.publisher< /index> </map> ><index> eg.keyword< /index> </map> ><index> eg.keyword< /index> </map>
<zurl>https:/
<option name="sru"
<charset>
<search>
<map use="4"
<map use="7"
<map use="8"
<map use="12"
<map use="21"
<map use="1003"
<map use="1018"
<map use="1035"
<map use="1016"
</search>
</database>
# dpkg -s yaz
Package: yaz
Architecture: amd64
Version: 5.23.0-1.indexdata