HTTPServer: Difference between revisions
(Created page with "== What is the built-in HTTP Server? == The GTA Connected server provides a built-in HTTP server which used to distribute client-side resource files to clients when they conne...") |
No edit summary |
||
| Line 3: | Line 3: | ||
== Do I need it? == | == Do I need it? == | ||
If you're hosting from your PC at home, the answer is most likely ''yes''. | If you're hosting from your PC at home, the answer is most likely '''yes'''. | ||
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. | 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. | ||
Revision as of 05:02, 23 August 2022
What is the built-in HTTP Server?
The GTA Connected server provides a built-in HTTP server which used to distribute client-side resource files to clients when they connect to the server (like audio, images, etc ... not scripts though).
Do I need it?
If you're hosting from your PC at home, the answer is most likely yes.
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 apache2 or 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.