Support > General Discussions
Application Server Users
Support:
I don't think this is a sbhttpd config issue. I would be seeing an error 500 from Apache if there were issue with SB. I can't see your Apache server even with trying port :8080 to override the port 80 default.
Support:
--- Code: Text ---ProxyPass /home/ http://127.0.0.1:8084/ProxyPassReverse /home/ http://127.0.0.1:8084/
--- Code: Text ---servers ( server ( port 8084 ip "127.0.0.1" protocol "http" ) threads 1024 listenbacklog 2 home "/var/www/vhosts/northwestliving.info/httpdocs/home/" proxyip 1
This is what I'm using for the northwestliving.info site with sbhttpd.
Support:
The proxyip determines if sbhttpd stands on it's own or in Apache's shadow.
I would use sbhttpd standalone as an application server on a intra-net. If your going to expose your site to the world, Apache is great for handling different connection speeds, (load leveling) the security layer and media delivery.
--- Quote ---I used scriba -k scriba.conf.unix.lsp when I first started to set sbhttpd up to get a clean scriba.conf.
--- End quote ---
Create a text version of your current scriba/sbhttpd binary configuration file.
scriba -D > basic.conf.text
Create a new binary format configuration file from your edited text version.
scriba -k basic.conf.txt
Navigation
[0] Message Index
[*] Previous page
Go to full version