- Koha - lists.katipo.co.nz

Koha 3.4: z39.50 public server configuration
by Abdul Vali 15 May '11

15 May '11

Hi I've installed Koha 3.4. I want to enable my server as public z39.50 server. I have the following config file: =========================== <yazgfs>    <listen id="biblioserver">tcp:@:9999</listen> <listen id="authorityserver">tcp:@:9998</listen>  <listen id="publicserver" >tcp:@:9999</listen>    <server id="biblioserver" listenref="biblioserver"> <directory>/var/lib/koha/zebradb/biblios</directory> <config>/etc/koha/zebradb/zebra-biblios.cfg</config> <cql2rpn>/etc/koha/zebradb/pqf.properties</cql2rpn>    <retrievalinfo> <retrieval syntax="usmarc" name="F"/> <retrieval syntax="usmarc" name="B"/> <retrieval syntax="xml" name="F"/> <retrieval syntax="xml" name="B"/> <retrieval syntax="xml" name="marcxml" identifier="info:srw/schema/1/marcxml-v1.1"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="xml" name="dc"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2DC.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="mods"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2MODS.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="rdfdc"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2RDFDC.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="rss2"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2RSS2.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="utils"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slimUtils.xsl"/> </backend> </retrieval> </retrievalinfo> <xi:include href="/etc/koha/zebradb/explain-biblios.xml" xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:fallback> <explain xmlns="http://explain.z3950.org/dtd/2.0/"> <serverInfo> <host>localhost</host> <port>9998</port> <database>biblios</database> </serverInfo> </explain> </xi:fallback> </xi:include> </server> <serverinfo id="biblioserver"> <ccl2rpn>/etc/koha/zebradb/ccl.properties</ccl2rpn> <user>kohauser</user> <password>zebrastripes</password> </serverinfo>  <server id="authorityserver" listenref="authorityserver" > <directory>/var/lib/koha/zebradb/authorities</directory> <config>/etc/koha/zebradb/zebra-authorities-dom.cfg</config> <cql2rpn>/etc/koha/zebradb/pqf.properties</cql2rpn>    <xi:include href="/etc/koha/zebradb/retrieval-info-auth-dom.xml" xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:fallback> <retrievalinfo> <retrieval syntax="usmarc" name="F"/> <retrieval syntax="usmarc" name="B"/> <retrieval syntax="xml" name="marcxml" identifier="info:srw/schema/1/marcxml-v1.1"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> </backend> </retrieval> <retrieval syntax="xml" name="dc"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2DC.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="mods"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2MODS.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="rdfdc"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slim2RDFDC.xsl"/> </backend> </retrieval> <retrieval syntax="xml" name="utils"> <backend syntax="usmarc" name="F"> <marc inputformat="marc" outputformat="marcxml" inputcharset="utf-8"/> <xslt stylesheet="/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/xslt/MARC21slimUtils.xsl"/> </backend> </retrieval> </retrievalinfo> </xi:fallback> </xi:include> <xi:include href="/etc/koha/zebradb/explain-authorities.xml" xmlns:xi="http://www.w3.org/2001/XInclude"> <xi:fallback> <explain xmlns="http://explain.z3950.org/dtd/2.0/"> <serverInfo> <host>localhost</host> <port>9999</port> <database>authorities</database> </serverInfo> </explain> </xi:fallback> </xi:include> </server> <serverinfo id="authorityserver"> <ccl2rpn>/etc/koha/zebradb/ccl.properties</ccl2rpn> <user>kohauser</user> <password>zebrastripes</password> </serverinfo>    <config> <db_scheme>mysql</db_scheme> <database>koha</database> <hostname>localhost</hostname> <port>3306</port> <user>kohaadmin</user> <pass>katikoan</pass> <biblioserver>biblios</biblioserver> <biblioservershadow>1</biblioservershadow> <authorityserver>authorities</authorityserver> <authorityservershadow>1</authorityservershadow> <intranetdir>/usr/share/koha/intranet/cgi-bin</intranetdir> <opacdir>/usr/share/koha/opac/cgi-bin/opac</opacdir> <opachtdocs>/usr/share/koha/opac/htdocs/opac-tmpl</opachtdocs> <intrahtdocs>/usr/share/koha/intranet/htdocs/intranet-tmpl</intrahtdocs> <includes>/usr/share/koha/intranet/htdocs/intranet-tmpl/prog/en/includes/</includes> <logdir>/var/log/koha</logdir> <pazpar2url>http://mykoha-laptop:11002/search.pz2</pazpar2url> <install_log>/usr/share/koha/misc/koha-install-log</install_log> <useldapserver>0</useldapserver> <memcached_servers></memcached_servers> <memcached_namespace></memcached_namespace> </config> </yazgfs> =========================== Now I'm trying to connect from other z39.50 client as: Hostname: mypublic ip Port: 9999 Database: biblios Syntax: MARC21/USMARC Encoding: UTF-8 But uanable to connect. Anything i am missing? How can I test? -- Regards Abdul Vali Librarian - ASE School

2 1

Generating barcodes in koha 3.4
by Somasekhar Rao K 15 May '11

15 May '11

Hi, I have trouble in generating barcodes. Can you please help me? In Home->Tools->Labels Home-> 1. When I manage Layouts, Templates, Profiles I could see the "Current Branch" as the library I am interested in. I was able to edit etc., and manage all above. 2. However, the moment I select "Managing Batches" or "New Batch", the overall library name that was set top right hand corner (next to kohaadmin, logout) gets reset and I don't see the library name against "Current Branch". If I go ahead with "New Batch" operation, select "Add Items" and choose the barcodes to be added to the batch, I get an error 404 saying the link is broken. Can you please help how to overcome this problem. Regards, Soma

3 3

Enabling Fast Cataloguing
by amutsikiwa 14 May '11

14 May '11

Hi I am running koha 3.2.6. I think I did not enable fast cataloguing during installation. I want to enable it now after installation. How do I go about it? Regards, Admire Mutsikiwa University of Zimbabwe

1 0

Re: [Koha] Enabling SSL for Koha staff view
by Randall Rowe 14 May '11

14 May '11

Direct from Apache.org SSL FAQ Why is it not possible to use Name-Based Virtual Hosting to identify different SSL virtual hosts? Name-Based Virtual Hosting is a very popular method of identifying different virtual hosts. It allows you to use the same IP address and the same port number for many different sites. When people move on to SSL, it seems natural to assume that the same method can be used to have lots of different SSL virtual hosts on the same server. It comes as rather a shock to learn that it is impossible. The reason is that the SSL protocol is a separate layer which encapsulates the HTTP protocol. So the SSL session is a separate transaction, that takes place before the HTTP session has begun. The server receives an SSL request on IP address X and port Y (usually 443). Since the SSL request does not contain any Host: field, the server has no way to decide which SSL virtual host to use. Usually, it will just use the first one it finds, which matches the port and IP address specified. You can, of course, use Name-Based Virtual Hosting to identify many non-SSL virtual hosts (all on port 80, for example) and then have a single SSL virtual host (on port 443). But if you do this, you must make sure to put the non-SSL port number on the NameVirtualHost directive, e.g. NameVirtualHost 192.168.1.1:80 Other workaround solutions include: Using separate IP addresses for different SSL hosts. Using different port numbers for different SSL hosts. Randy Rowe Lincoln City Libraries I.T. -----Original Message----- From: "Martin Renvoize" <martin.renvoize(a)ptfs-europe.com> Sent 5/13/2011 3:33:09 AM To: "Mizst Audens" <mizstik(a)gmail.com> Cc: koha(a)lists.katipo.co.nz Subject: Re: [Koha] Enabling SSL for Koha staff view You could however, Use Name based Virtualhosts (like kohaapoc.yourlibrary.com and kohastaff.yourlibrary.com) and run both on port 443 for secure. To do this you'll either need two certificates (one for each domain) or a SAN shared certificate with both domain names in it. An example http.conf might look like (assuming the two certificate approach); ## OPAC Default Access <VirtualHost 127.0.1.1:80> DocumentRoot /home/koha/kohaclone/koha-tmpl ServerName kohalibrary.halton.gov.uk . . . </VirtualHost> ## OPAC Secure <VirtualHost 127.0.1.1:443> DocumentRoot /home/koha/kohaclone/koha-tmpl ServerName kohalibrary.halton.gov.uk . . . # SSL Setup # CA Root and Intermediate Certificates SSLEngine On SSLCACertificatePath /etc/apache2/ssl/certs/ SSLCACertificateFile /etc/apache2/ssl/certs/gs_combined_ca.crt SSLCertificateFile /etc/apache2/ssl/certs/kohalibrary.crt SSLCertificateKeyFile /etc/apache2/ssl/certs/kohalibrary.key </VirtualHost> ## Intranet Secure <VirtualHost 109.75.173.120:443> DocumentRoot /home/koha/kohaclone/koha-tmpl ServerName kohastaff.halton.gov.uk . . . # SSL Setup # CA Root and Intermediate Certificates SSLEngine On SSLCACertificatePath /etc/apache2/ssl/certs/ SSLCACertificateFile /etc/apache2/ssl/certs/gs_combined_ca.crt SSLCertificateFile /etc/apache2/ssl/certs/kohastaff.crt SSLCertificateKeyFile /etc/apache2/ssl/certs/kohastaff.key </VirtualHost> 2011/5/8 Mizst Audens <mizstik(a)gmail.com> No, it's not possible due to the limitation of the architecture. A port can serve only http or https but not both at the same time. The transparency of http/https in normal websites is due to the standardization of port 80 and 443. (port 80 runs http, and port 443 runs https, so each port only runs one type of connection) When you don't use these standard ports, you will need to specify the correct combination of protocol and port in order to reach a service. --Mizst On Sun, May 8, 2011 at 12:33 PM, Altaf Mahmud <altaf.mahmud(a)gmail.com> wrote: Is it possible to use port 8080 for both purposes (HTTP and HTTPS)? Actually, I just wanted to secure port 8080, can I do that? Thanks a lot! On Sat, May 7, 2011 at 8:34 PM, Mizst Audens <mizstik(a)gmail.com> wrote: You must create another virtual host at another port (for example, 8081) for the staff area and enable SSL for that virtual host, and it will require another SSL certificate. Your staff will need to use (example) https://127.0.1.1:8081 if they want to use SSL, and http://127.0.1.1:8080 if they don't want to use SSL. Note that https://127.0.1.1 is in fact an alias for https://127.0.1.1:443. You already used 443 for the OPAC, so you'll need another port for the staff. --Mizst 2011/5/7 Altaf Mahmud <altaf.mahmud(a)gmail.com> Hello, I'm trying to implement SSL in my Koha server running on Debian 6.0 (squeeze). I've implemented it for my OPAC view, I've created another file 'koha-ssl' in ../apache2/sites-available/ directory and enabled it. I've edited ../apache2/sites-available/koha like following: NameVirtualHost *:80 <VirtualHost 127.0.1.1:80> ..... ..... </VirtualHost> And ../apache2/sites-available/koha-ssl like following: NameVirtualHost *:443 <VirtualHost 127.0.1.1:443> ..... SSLEngine On SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key ..... </VirtualHost> Now https://127.0.1.1/ is showing the OPAC. But I can't figure it out how to implement it for staff-view <VirtualHost 127.0.1.1:8080> Request for port 80 is redirecting to port 443, how can I do that for port 8080? In fact, I don't have any prior idea on doing this; a descriptive suggestion is appropriate for me. Thanks. -- Altaf Mahmud System Programmer Ayesha Abed Library BRAC University Bangladesh. _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Altaf Mahmud System Programmer Ayesha Abed Library BRAC University Bangladesh. _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha -- Martin Renvoize Software Developer, PTFS Europe Ltd Content Management and Library Solutions martin.renvoize(a)ptfs-europe.com skype: Martin Renvoize http://www.ptfs-europe.com _______________________________________________ Koha mailing list http://koha-community.org Koha(a)lists.katipo.co.nz http://lists.katipo.co.nz/mailman/listinfo/koha

4 5

Koha LTS (Long Term Support) and ..
by Abdul Vali 13 May '11

13 May '11

Dear wonderful community of koha I am not a programmer and have a little know how of technical things involved in koha. i have seen that koha community and developers are so active that new versions of koha are coming regularly and it is very difficult for us to keep us align with the pace of this development. is there any way to release some Long Term Support (LTS) version of koha just like Ubuntu LTS? - can we install koha latest version using apt-get install koha by adding the sources in sources.list of ubuntu, debian or fedora? similarly we may able to use apt-get update and remove command for koha? in my point of view many users who are not well aware of linux installation process can use koha easily - will koha shift to postgresql and solr instead of mysql and zebra respectively? -- Abdul Vali Librarian - ASE School

1 0

Error when saving Marc record
by library＠holyfamilyca.org 13 May '11

13 May '11

1 0

Re: [Koha] LibLive
by Adalid Ortiz 13 May '11

13 May '11

Yes, this live-cd comes with Dsapce. If you want the Wubi installer that work for me I will send you. Saludos Adalid Ortiz Biblioteca Loyola http://www.tij.uia.mx UPS ! Hablas español.... JAJAJA... OK > >Subject: LibLive > From: Hugo Agud <hagud(a)orex.es> > Date: Fri, 13 May 2011 09:26:01 +0200 > To: adalid(a)tij.uia.mx > >--0023547c895decf2e704a3233818 >Content-Type: text/plain; charset=ISO-8859-1 >Content-Transfer-Encoding: quoted-printable > >Hi Adalib > >thank you very much for info, just one question is there any kind of >integration between koha and dspace in this live CD? > >Once again thank you very much!!!! > >-- > >*Hugo Agud - Orex Digital * > >*www.orex.es* > >* >* > > Director > >Avenida Sarriá 29 · 08029 Barcelona <http://twitter.com/OrexDigital> >:<http://orexsl.blogspot.com>hugoaguda - Tel: 638 799 704 >hagud(a)orex.es · http://www.orex.es/ > > > >No imprima este mensaje a no ser que sea necesario. Una tonelada de papel >implica la tala de 15 árboles y el consumo de 250.000 litros de agua. > > > >Aviso de confidencialidad >Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO >RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni >está autorizado a recibirlo por el remitente), no está autorizado a copiar, >reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje >por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema. > >--0023547c895decf2e704a3233818 >Content-Type: text/html; charset=ISO-8859-1 >Content-Transfer-Encoding: quoted-printable > >Hi Adalib<div> </div><div>thank you very much for info, just one question is there any kind of integration between koha and dspace in this live CD?</div><div> </div><div>Once again thank you very much!!!! > > -- > >Hugo Agud - Orex Digital > ><a href="http://www.orex.es" target="_blank">www.orex.es</a> > > > ><table border="0" cellspacing="0" cellpadding="0" width="823" style="width:617.25pt"> > ><tbody><tr><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > >Director</td></tr><tr><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > ></td></tr><tr><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > >Avenida Sarriá 29 · 08029 Barcelona <a href="http://twitter.com/OrexDigital" target="_blank"><img src="http://www.orex.es/images/website/templateImages/originals/Logotwitter.jpg"></a> <img src="http://orex.gmt.brightpearl.com/images/website/templateImages/originals/sky…"> <a href="http://orexsl.blogspot.com" target="_blank"><img src="http://orex.gmt.brightpearl..com/images/website/templateImages/originals/mi…">:</a> hugoaguda - Tel: 638 799 704 <a href="mailto:hagud@orex.es" target="_blank">hagud(a)orex.es</a> · <a href="http://www.orex.es/" style="color:rgb(42, 93, 176)" target="_blank">http://www.orex.es/</a> > ></td></tr><tr><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > > </td></tr><tr><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > >No imprima este mensaje a no ser que sea necesario. Una tonelada de papel implica la tala de 15 árboles y el consumo de 250.000 litros de agua.</td></tr><tr> > ><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > > </td></tr><tr><td colspan="8" style="margin-top:0px;margin-right:0px;margin-bottom:0px;margin-left:0px;font-family:arial, sans-serif;padding-top:0cm;padding-right:0cm;padding-bottom:0cm;padding-left:0cm"> > >Aviso de confidencialidad Este mensaje contiene información que puede ser CONFIDENCIAL y/o de USO RESTRINGIDO. Si usted no es el receptor deseado del mensaje (ni > >está autorizado a recibirlo por el remitente), no está autorizado a copiar, reenviar o divulgar el mensaje o su contenido. Si ha recibido este mensaje > >por error, por favor, notifíquenoslo inmediatamente y bórrelo de su sistema.</td></tr></tbody></table> ></div> > >--0023547c895decf2e704a3233818--

1 0

Koha OPAC usage log
by Agnes Rivers-Moore 13 May '11

13 May '11

Hello all Is there a way to extract usage statistics for the public catalogue of Koha? I would like to be able to make a report that would show daily numbers of main page access, number of searches, number of holds placed, number of renewals done by our patrons through the OPAC. Does anyone have a method for this? Is there a log file we could query to generate these number? Has anyone added a web page analytics thing to get this kind of usage information? We are on 3.00.06, moving to 3.2 soon. Thank you Agnes -- CEO/ Chief Librarian Hanover Public Library. 451 10th Ave, Hanover, ON N4N 2P1 Tel: 519-364-1420 Email: arm(a)hanover.ca Please consider the environment before printing this message or attachments. Support your library! Please consider making a donation, joining the Friends of the Library, or remembering us in your will. -- This email was Anti Virus checked by Astaro Security Gateway. http://www.astaro.com

3 3

Sudden problem with check in
by Peel Lisa 13 May '11

13 May '11

Hello All of a sudden we are having a problem when checking in some items - we keep getting the message 'this item needs to be transferred to IHCR. Transfer now?' even when the item is being checked in at IHCR and the borrower also has the location IHCR. It is doing this sparodically (different patrons, different item types) and I can't see any pattern so it is hard to duplicate, it seems to be happening (at the moment) only at one location. Any ideas? What does Circ use to determine location (I had assumed from the location chosen when logging in)? And why has it only just started to happen (been running Koha since last August). We are on 3.00.05 (hoping to upgrade very soon!!) Regards Lisa [Description: Description: Description: CR_logo_POS_COULEUR b] LISA PEEL, PGDip, MA. Librarian César Ritz Colleges Switzerland 1897 Le Bouveret - Switzerland Tel: +41 24 482 82 82 Fax: +41 24 482 82 80 E-mail: lisa.peel(a)ritz.edu<mailto:hortense.hofer@ritz.edu> http://www.ritz.edu<http://www.ritz.edu/> - http://www.culinaryarts.ch<http://www.culinaryarts.ch/>

2 1

Re: [Koha] Enabling SSL for Koha staff view
by Mizst Audens 13 May '11

13 May '11

In some situations it does work (a little mysteriously IMO). For example, I have these in my private home server and it does work correctly (verified extensively): <VirtualHost *:443> DocumentRoot /var/www ServerName app1.home.mysite.com SSLCertificateFile app1cert.crt ... (other SSL directives) and: <VirtualHost _default_:443> DocumentRoot /var/www ServerName home.mysite.com SSLCertificateFile homecert.crt ... (other SSL directives) It works correctly for both app1.home.mysite.com and home.mysite.com. And app1 does not work when I remove the *:443 virtualhost. Furthermore, SSL will most certainly work, even in principle, if you use one wildcard subdomain certificate in conjunction with multiple virtualhosts. What you cannot do is put two SSL directives in one virtualhost, in which case the second is ignored. However, in the original topic, the server in question used IP:Port to identify the virtualhosts so he could not use this technique. --Mizst On Fri, May 13, 2011 at 6:40 PM, Randall Rowe <r.rowe(a)lincolnlibraries.org>wrote: > Direct from Apache.org SSL FAQ<http://httpd.apache.org/docs/2.0/ssl/ssl_faq.html> > > Why is it not possible to use Name-Based Virtual Hosting to identify > different SSL virtual hosts? > > Name-Based Virtual Hosting is a very popular method of identifying > different virtual hosts. It allows you to use the same IP address and the > same port number for many different sites. When people move on to SSL, it > seems natural to assume that the same method can be used to have lots of > different SSL virtual hosts on the same server. > > It comes as rather a shock to learn that it is impossible. > > The reason is that the SSL protocol is a separate layer which encapsulates > the HTTP protocol. So the SSL session is a separate transaction, that takes > place before the HTTP session has begun. The server receives an SSL request > on IP address X and port Y (usually 443). Since the SSL request does not > contain any Host: field, the server has no way to decide which SSL virtual > host to use. Usually, it will just use the first one it finds, which matches > the port and IP address specified. > > You can, of course, use Name-Based Virtual Hosting to identify many non-SSL > virtual hosts (all on port 80, for example) and then have a single SSL > virtual host (on port 443). But if you do this, you must make sure to put > the non-SSL port number on the NameVirtualHost directive, e.g. > > NameVirtualHost 192.168.1.1:80 > > Other workaround solutions include: > > Using separate IP addresses for different SSL hosts. Using different port > numbers for different SSL hosts. > > > Randy Rowe > Lincoln City Libraries I.T. > > > > > -----Original Message----- > From: "Martin Renvoize" <martin.renvoize(a)ptfs-europe.com> > Sent 5/13/2011 3:33:09 AM > To: "Mizst Audens" <mizstik(a)gmail.com> > Cc: koha(a)lists.katipo.co.nz > Subject: Re: [Koha] Enabling SSL for Koha staff view > > > You could however, > > Use Name based Virtualhosts (like kohaapoc.yourlibrary.com and > kohastaff.yourlibrary.com) and run both on port 443 for secure. To do > this you'll either need two certificates (one for each domain) or a SAN > shared certificate with both domain names in it. > > An example http.conf might look like (assuming the > two certificate approach); > > ## OPAC Default Access > <VirtualHost 127.0.1.1:80> > DocumentRoot /home/koha/kohaclone/koha-tmpl > ServerName kohalibrary.halton.gov.uk > . . . > </VirtualHost> > > ## OPAC Secure > <VirtualHost 127.0.1.1:443> > DocumentRoot /home/koha/kohaclone/koha-tmpl > ServerName kohalibrary.halton.gov.uk > . . . > > # SSL Setup > # CA Root and Intermediate Certificates > SSLEngine On > SSLCACertificatePath /etc/apache2/ssl/certs/ > SSLCACertificateFile /etc/apache2/ssl/certs/gs_combined_ca.crt > > SSLCertificateFile /etc/apache2/ssl/certs/kohalibrary.crt > SSLCertificateKeyFile /etc/apache2/ssl/certs/kohalibrary.key > > </VirtualHost> > > ## Intranet Secure > <VirtualHost 109.75.173.120:443> > DocumentRoot /home/koha/kohaclone/koha-tmpl > ServerName kohastaff.halton.gov.uk > . . . > # SSL Setup > # CA Root and Intermediate Certificates > SSLEngine On > SSLCACertificatePath /etc/apache2/ssl/certs/ > SSLCACertificateFile /etc/apache2/ssl/certs/gs_combined_ca.crt > > SSLCertificateFile /etc/apache2/ssl/certs/kohastaff.crt > SSLCertificateKeyFile /etc/apache2/ssl/certs/kohastaff.key > </VirtualHost> > > > > 2011/5/8 Mizst Audens <mizstik(a)gmail.com> > >> No, it's not possible due to the limitation of the architecture. A port >> can serve only http or https but not both at the same time. >> >> The transparency of http/https in normal websites is due to the >> standardization of port 80 and 443. (port 80 runs http, and port 443 runs >> https, so each port only runs one type of connection) When you don't use >> these standard ports, you will need to specify the correct combination of >> protocol and port in order to reach a service. >> >> --Mizst >> >> >> On Sun, May 8, 2011 at 12:33 PM, Altaf Mahmud <altaf.mahmud(a)gmail.com>wrote: >> >>> Is it possible to use port 8080 for both purposes (HTTP and HTTPS)? >>> Actually, I just wanted to secure port 8080, can I do that? >>> >>> Thanks a lot! >>> >>> >>> On Sat, May 7, 2011 at 8:34 PM, Mizst Audens <mizstik(a)gmail.com> wrote: >>> >>>> You must create another virtual host at another port (for example, 8081) >>>> for the staff area and enable SSL for that virtual host, and it will require >>>> another SSL certificate. Your staff will need to use (example) >>>> https://127.0.1.1:8081 if they want to use SSL, and >>>> http://127.0.1.1:8080 if they don't want to use SSL. >>>> >>>> Note that https://127.0.1.1 is in fact an alias for >>>> https://127.0.1.1:443. You already used 443 for the OPAC, so you'll >>>> need another port for the staff. >>>> >>>> --Mizst >>>> >>>> >>>> 2011/5/7 Altaf Mahmud <altaf.mahmud(a)gmail.com> >>>> >>>>> Hello, >>>>> >>>>> I'm trying to implement SSL in my Koha server running on Debian 6.0 >>>>> (squeeze). I've implemented it for my OPAC view, I've created another file >>>>> 'koha-ssl' in ../apache2/sites-available/ directory and enabled it. I've >>>>> edited ../apache2/sites-available/koha like following: >>>>> >>>>> NameVirtualHost *:80 >>>>> <VirtualHost 127.0.1.1:80> >>>>> >>>>> ..... >>>>> ..... >>>>> >>>>> </VirtualHost> >>>>> >>>>> And ../apache2/sites-available/koha-ssl like following: >>>>> >>>>> NameVirtualHost *:443 >>>>> <VirtualHost 127.0.1.1:443> >>>>> ..... >>>>> >>>>> SSLEngine On >>>>> SSLCertificateFile /etc/ssl/certs/ssl-cert-snakeoil.pem >>>>> SSLCertificateKeyFile /etc/ssl/private/ssl-cert-snakeoil.key >>>>> >>>>> ..... >>>>> </VirtualHost> >>>>> >>>>> Now https://127.0.1.1/ is showing the OPAC. But I can't figure it out >>>>> how to implement it for staff-view <VirtualHost 127.0.1.1:8080> >>>>> Request for port 80 is redirecting to port 443, how can I do that for >>>>> port 8080? In fact, I don't have any prior idea on doing this; a descriptive >>>>> suggestion is appropriate for me. >>>>> >>>>> Thanks. >>>>> >>>>> >>>>> >>>>> -- >>>>> Altaf Mahmud >>>>> System Programmer >>>>> Ayesha Abed Library >>>>> BRAC University >>>>> Bangladesh. >>>>> >>>>> >>>>> _______________________________________________ >>>>> Koha mailing list http://koha-community.org >>>>> Koha(a)lists.katipo.co.nz >>>>> http://lists.katipo.co.nz/mailman/listinfo/koha >>>>> >>>>> >>>> >>> >>> >>> -- >>> Altaf Mahmud >>> System Programmer >>> Ayesha Abed Library >>> BRAC University >>> Bangladesh. >>> >>> >> >> _______________________________________________ >> Koha mailing list http://koha-community.org >> Koha(a)lists.katipo.co.nz >> http://lists.katipo.co.nz/mailman/listinfo/koha >> >> > > > -- > Martin Renvoize > Software Developer, PTFS Europe Ltd > Content Management and Library Solutions > martin.renvoize(a)ptfs-europe.com > skype: Martin Renvoize > > http://www.ptfs-europe.com > > _______________________________________________ > Koha mailing list http://koha-community.orgKoha@lists.katipo.co.nzhttp://lists.katipo.co.nz/m… > >

1 0