HTTPServer: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
No edit summary
Line 12: Line 12:


== 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. 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. 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
* Tweak how the HTTP service distributes the files (connection/bandwidth limits, firewall, etc)
* 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]
2,603

edits

Navigation menu