On Fri, Feb 29, 2008 at 4:38 PM, Jesse <<a href="mailto:pianohacker@gmail.com">pianohacker@gmail.com</a>> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div class="Ih2E3d"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Right now, I've taken to accessing the Intranet on Firefox and the OPAC on MSIE to keep my logins separate. But could this problem be solved if Koha used different cookie names for the two different sections? e.g. instead of using CGISESSID everywhere, maybe use KOHAINET as the cookie name for the Intranet and KOHAOPAC for the OPAC site?<br>
<br>
Is this worth submitting an enhancement request over?</blockquote></div><div></div></div></blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="gmail_quote"><div><br>Possibly, but the usual solution would be vhosts (<a href="http://staff/" target="_blank">http://staff/</a> would be your intranet, <a href="http://opac/" target="_blank">http://opac/</a>, your OPAC).</div>
</div></blockquote><div><br>Specifically, using name-based VirtualHosts or variously named VirtualHosts on different interfaces (IPs) would put the two cookies into different namespaces, so they would not conflict in any browser (in fact, they would be protected from cross-site access, since to the browser they would be different sites).<br>
</div></div><br>But your idea about keeping the cookies separately named is a good one.<br><br>--Joe Atzberger<br>