That, too, would require the Koha host have an external IP. The iframe simply puts a wrapper around the web page, it doesn’t redirect the content.
Aaron -- Aaron Sakovich Internet and Technology Services Manager Huntsville-Madison County Public Library 915 Monroe Street | Huntsville, Alabama 35801 | https://hmcpl.org/ > On Jun 26, 2020, at 10:16, Alvaro Cornejo <[email protected]> wrote: > > Hi > > What about embed opac inside a frame into your IIS? > > Regards > > Alvaro > |----------------------------------------------------------------------------------------| > Stay safe / Cuídate/ Reste sécurisé > 7 Switch off as you go / Apaga lo que no usas / Débranchez au fur et à > mesure. > q Recycle always / Recicla siempre / Recyclez toujours > P Print only if absolutely necessary / Imprime solo si es necesario / > Imprimez seulement si nécessaire > > > Le ven. 26 juin 2020 à 09:47, [email protected] > <mailto:[email protected]> <[email protected] > <mailto:[email protected]>> a écrit : > Greetings, Bravismore, > > That won’t work — the execution of the scripts is done on the Koha host, and > would never work on an IIS host. If they were pure HTML files, yeah, it might > work. But the IIS server would see Perl files via a Samba share, not HTML > output. > > An approach that would work would be to setup a proxy on the IIS host that > would reroute requests to and from the Koha server. However, setting up a > proxy is fraught with severe security risks. I would strongly discourage that > unless you have an IIS expert in house with a lot of proxy experience. > > The best solution is to expose the OPAC interface to the Internet, for > performance, simplicity, stability, and security reasons — that is why most > libraries do that. > > Aaron > -- > Aaron Sakovich > Internet and Technology Services Manager > > Huntsville-Madison County Public Library > 915 Monroe Street | Huntsville, Alabama 35801 | https://hmcpl.org/ > <https://hmcpl.org/> > > > > > > On Jun 26, 2020, at 08:10, Mumanyi, Bravismore <[email protected] > > <mailto:[email protected]>> wrote: > > > > Dear Koha Community > > > > I have a Koha site that intends to publish their mature WebPAC to the globe. > > However, they decline to assign a public IP and DN. > > > > Their preferred route is to serve KOHA pages via their website hosted on > > Windows/IIS. > > Koha is on Ubuntu/Apache2 webserver. > > > > I had thought of using samba to share the Koha opac DocumentRoot, then > > create a virtualhost equivalent on IIS. > > > > Before I labour on this, any Koha geeks out there who can advise if this > > will technically work? > > > > Thank you > > > > Regards > > /Bravismore > > _______________________________________________ > > > > Koha mailing list http://koha-community.org <http://koha-community.org/> > > [email protected] <mailto:[email protected]> > > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > > <https://lists.katipo.co.nz/mailman/listinfo/koha> > > _______________________________________________ > > Koha mailing list http://koha-community.org <http://koha-community.org/> > [email protected] <mailto:[email protected]> > Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha > <https://lists.katipo.co.nz/mailman/listinfo/koha> _______________________________________________ Koha mailing list http://koha-community.org [email protected] Unsubscribe: https://lists.katipo.co.nz/mailman/listinfo/koha
