Interface administrators, moderator
2,601
edits
HTTPServer: Difference between revisions
no edit summary
No edit summary |
No edit summary |
||
| Line 14: | Line 14: | ||
Turning off the built-in HTTP server is typically for server owners or hosts that want to use another HTTP service like [https://httpd.apache.org/ apache2] or [https://nginx.org/en/ nginx] to distribute the client resource files. Doing this can also help improve performance of the host if you run more than one server using the same resources, need to tweak how the HTTP service distributes the files (connection/bandwidth limits, firewall, etc), or if the server isn't loading any resources that contain client-side files. | Turning off the built-in HTTP server is typically for server owners or hosts that want to use another HTTP service like [https://httpd.apache.org/ apache2] or [https://nginx.org/en/ nginx] to distribute the client resource files. Doing this can also help improve performance of the host if you run more than one server using the same resources, need to tweak how the HTTP service distributes the files (connection/bandwidth limits, firewall, etc), or if the server isn't loading any resources that contain client-side files. | ||
You can also change the HTTP url using the <httpurl> in your server configuration. This will make clients that connect to the server use that URL to grab the client resource files. This is useful if you want to use a [ | You can also change the HTTP url using the <httpurl> in your server configuration. This will make clients that connect to the server use that URL to grab the client resource files. This is useful if you want to use a [https://en.wikipedia.org/wiki/Content_delivery_network CDN] | ||