On Sat, May 14, 2011 at 7:06 AM, MJ Ray wrote:
> Mizst Audens wrote:
> > Your server returned a 400 Bad Request for the http on port 443. :-)
>
> Yes, it detected the http and served you html, did you notice? :-)
> Only an error message, but as I wrote: serving http seamlessly is
> probably a bad
Mizst Audens wrote:
> Your server returned a 400 Bad Request for the http on port 443. :-)
Yes, it detected the http and served you html, did you notice? :-)
Only an error message, but as I wrote: serving http seamlessly is
probably a bad idea (easy to lose security by typo).
> But glad to hear
who knows perfection koha install??
2011/5/13 Mizst Audens
> Your server returned a 400 Bad Request for the http on port 443. :-) But
> glad to hear that SNI is going to come standard now, at least in some
> distro.
>
> I think that information pertaining to Koha deployment should be considered
Your server returned a 400 Bad Request for the http on port 443. :-) But
glad to hear that SNI is going to come standard now, at least in some
distro.
I think that information pertaining to Koha deployment should be considered
relevant to the list, and in my opinion that includes some nuances of a
Randall Rowe wrote:
> Direct from Apache.org SSL FAQ
Yeah, sorry, that's out of date. With recent browsers and recent
Apache modules you can have multiple SSL VirtualHosts on one IP. See
https://sni.velox.ch/ for how it works and my last sig link if you'd
like the co-op to get the SSLs and/or se
gt; Lincoln City Libraries I.T.
>
>
>
>
> -Original Message-----
> From: "Martin Renvoize"
> Sent 5/13/2011 3:33:09 AM
> To: "Mizst Audens"
> Cc: koha@lists.katipo.co.nz
> Subject: Re: [Koha] Enabling SSL for Koha staff view
>
>
> You
hosts.
Randy Rowe
Lincoln City Libraries I.T.
-Original Message-
From: "Martin Renvoize"
Sent 5/13/2011 3:33:09 AM
To: "Mizst Audens"
Cc: koha@lists.katipo.co.nz
Subject: Re: [Koha] Enabling SSL for Koha staff view
You could however,
Use Name base
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 mi
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 run
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 wrote:
> You must create another virtual host at another port (for example, 8081)
> for the staff area and e
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'
11 matches
Mail list logo
