Interface administrators, moderator
2,603
edits
HTTPServer: Difference between revisions
Jump to navigation
Jump to search
no edit summary
No edit summary |
No edit summary |
||
| Line 13: | Line 13: | ||
== For advanced users == | == For advanced users == | ||
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. This can also help improve performance of the host machine if you want to do any of the following: | 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. This can also help improve performance of the host machine if you want to do any of the following: | ||
* Run than one server using the same resources | * Run more than one server using the same resources | ||
* Tweak how the HTTP service distributes the files (connection/bandwidth limits, firewall, etc) | * Tweak how the HTTP service distributes the files (connection/bandwidth limits, firewall, etc) | ||
* Not load any resources that contain client-side files. | * Not load 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 [https://en.wikipedia.org/wiki/Content_delivery_network CDN] | 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] | ||