<br><br><div class="gmail_quote">On Sat, May 14, 2011 at 7:06 AM, MJ Ray <span dir="ltr"><<a href="mailto:mjr@phonecoop.coop">mjr@phonecoop.coop</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div class="im">Mizst Audens wrote:<br>
> Your server returned a 400 Bad Request for the http on port 443. :-)<br>
<br>
</div>Yes, it detected the http and served you html, did you notice? :-)<br>
Only an error message, but as I wrote: serving http seamlessly is<br>
probably a bad idea (easy to lose security by typo).<br>
<div class="im"><br></div></blockquote><div> </div><div>Oh I thought that was a standard error message or something, since my server does the same thing without any configuration. And anyway I thought you were referring to serving a functioning page, not an error message.</div>
<div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> But glad to hear that SNI is going to come standard now, at least in some<br>
> distro.<br>
><br>
> I think that information pertaining to Koha deployment should be considered<br>
> relevant to the list, and in my opinion that includes some nuances of all<br>
> the facilities that Koha requires for its operations and for the needs of<br>
> the library, in this case adding security for the staff interface.<br>
<br>
</div>Sorry, but I feel the list needs a limit. Configuring Apache HTTPD<br>
isn't specific to Koha, there is plenty of help available on more<br>
mainstream sites and the Koha list seems pretty busy with Koha<br>
questions already, without adding the setup of Apache, MySQL and<br>
GNU/Linux to it. Also, there are other ways to secure the staff<br>
interface without dealing with this, such as a VPN.<br>
<div class="im"><br></div></blockquote><div><br></div><div>Yes, there needs to be some limit, but I think not having this in Koha list is counter productive. We at least need to be able to discuss the issues that Koha users can run into, or what kind of config is best when trying to run Koha, etc. Same thing with setting up mail for Koha and that sort of thing. All the posts stay in its own topic anyway.</div>
<div><br></div><div>Sure, you can use VPN. And you can use SSL. So?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div class="im">
> Surely, anyone considering to add SSL to their Koha server is going<br>
> to run into these issues.<br>
<br>
</div>Surely not? I think most users run only one Koha.<br>
<br></blockquote><div><br></div><div>See TC's post. He was trying to add SSL to both OPAC and staff area. That makes it two virtualhosts, and he did run into a problem trying to get SSL to work.</div><div> </div><div>
--Mizst</div><div><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
Regards,<br>
<font color="#888888">--<br>
</font><div><div></div><div class="h5">MJ Ray (slef), member of <a href="http://www.software.coop" target="_blank">www.software.coop</a>, a for-more-than-profit co-op.<br>
<a href="http://koha-community.org" target="_blank">http://koha-community.org</a> supporter, web and LMS developer, statistician.<br>
In My Opinion Only: see <a href="http://mjr.towers.org.uk/email.html" target="_blank">http://mjr.towers.org.uk/email.html</a><br>
Available for hire for Koha work <a href="http://www.software.coop/products/koha" target="_blank">http://www.software.coop/products/koha</a><br>
_______________________________________________<br>
Koha mailing list <a href="http://koha-community.org" target="_blank">http://koha-community.org</a><br>
<a href="mailto:Koha@lists.katipo.co.nz">Koha@lists.katipo.co.nz</a><br>
<a href="http://lists.katipo.co.nz/mailman/listinfo/koha" target="_blank">http://lists.katipo.co.nz/mailman/listinfo/koha</a><br>
</div></div></blockquote></div><br>