system
(system)
February 25, 2006, 5:31am
1
ajperezcrespo wrote on Saturday, February 25, 2006 :
My apache2 is set for ssl
OEMR (CVS) works fine
SQL-Ledger (2.6.6) Works Fine
I get payload errors when they talk to each other with SSL active.
freeb.conf
https://localhost:443 …
Globals.php accounting system web serv integrations
port "443"
url_path "https://"
Any other files that need to be modified?
Thanks
Alfonso
system
(system)
February 25, 2006, 5:43am
2
sunsetsystems wrote on Saturday, February 25, 2006 :
I’ve not tried it that way. You may be better off letting Apache listen on localhost:80 in addition to port 443 on the network.
– Rod
www.sunsetsystems.com
system
(system)
February 25, 2006, 12:22pm
3
ajperezcrespo wrote on Saturday, February 25, 2006 :
True but dont we need to encrypt for HIPAA compliance? Especially if on WIFI we dont want Patient data floating around.
Thanks
system
(system)
February 25, 2006, 2:09pm
4
sunsetsystems wrote on Saturday, February 25, 2006 :
I was suggesting encryption (port 443) for network communication, and non-encryption (port 80) just for the case where the server talks to itself, as when using XML/RPC over HTTP to communicate with SQL-Ledger.
– Rod
www.sunsetsystems.com
system
(system)
February 27, 2006, 4:39pm
5
andres_paglayan wrote on Monday, February 27, 2006 :
the config way to do so, it’s only allowing port 80 to the localhost inside the <directyory> directive