| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| howto:apache [2010/03/20 18:28] – tracker1 | howto:apache [2018/03/01 12:21] (current) – old revision restored digital man |
|---|
| |
| ===== MOD_PROXY ===== | ===== MOD_PROXY ===== |
| Probably the best way to integrate Synchronet behind Apache is to configure MOD_PROXY on the apache side, to redirect calls to *.ssjs forward to Synchronet's HTTP server running on a separate port. It's worth noting that the current SBBS web interface is setup to use HTTP Authentication, and would need to be adjusted to support a cookie based authentication scheme. By configuring Apache to use the same directory as SBBS, you can rely on Apache to perform caching and compression of non-dynamic content to be delivered directly. | Probably the best way to integrate Synchronet behind Apache is to [[http://www.google.com/search?q=apache+mod_proxy+reverse+proxy|configure MOD_PROXY on Apache]] to reverse-proxy calls for .ssjs files to Synchronet's HTTP server running on a different port. It's worth noting that the current SBBS web interface is setup to use HTTP Authentication, and would need to be adjusted to support a cookie based authentication scheme. By configuring Apache to use the same directory as SBBS, you can rely on Apache to perform caching and compression of non-dynamic content to be delivered directly. |
| |
| ===== IIS ===== | ===== IIS ===== |
| |
| ===== See Also ===== | ===== See Also ===== |
| * [[custom:js|JavaScript]] | * [[custom:javascript|JavaScript]] |
| * [[util:JSexec]] | * [[util:JSexec]] |
| * [[:howto:|HowTo index]] | * [[:howto:|HowTo index]] |
