#GitHub - RaphaelIT7/gmod-httpserver
1 messages · Page 1 of 1 (latest)
But it's the reason why I made it. I had nothing to do.
this sounds incredibly useful, not sure what i'd use it for yet but there must be some usecases
Alternative networking channel, we just talked about it in #next-update . We joked about using a custom HTTP server for ingame networking with HTTP() functions and then it arives like orderd. 
i feel like this would be a big target for ddoses tho
as @shadow summit mentioned in dms, it might be cool if it had a IP whitelist of only connected players, or an option to manually add whitelisted ips etc
I will try to add one.
this could possibly be paired with gm_express, that'd be really sick
I created an example for networking stuff(https://github.com/RaphaelIT7/gmod-httpserver/blob/main/examples/httpnet.lua), but I never tried to use gm_express. It could work, but it wouldn't be that fast, because an HTTP request takes from 50 up to 150ms and sometimes a bit more.
hm
while running performance tests for gm_express, I found that HTTP requests started being better (in terms of raw speed) for payloads bigger than ~192kb.
while express is free to use as-is (cloud hosted), you can also self-host it in a docker container.
letting people self-host it using only this dll and lua addons would be pretty cool
looks nice, well done!
But express is almost incomparable to this, express uses edge servers (according to your documentation)
It’s always going to be faster than connecting directly to a gmod server somewhere in the world especially without geo balancing
Also unlike express running any form of direct host on your server just gives people a new surface of attack. Your gmod host may be able to block game attacks etc but chances are it’s not also expecting to have to handle HTTP traffic ontop
This + Proxy is very good, isn’t something that should be ran alone imo
most hosts wont allow you to run a http service anyways if they even allow you opening ports at all tho
but this can still be useful for some
I made a very similar web server a while back using luasockets, and then rewrote it not long ago to use websocket connections only
(Below is literally the only image I have of it on my phone)
That way you can have an upstream gateway/proxy to do the bulk of request validation like authentication and route checking etc
Since originally I was using luasockets and basic flood tests would always crash the server
You want the request to be terminated as soon as possible if it’s just junk, hence why a proxy is so important
This is still good though, I’m just stressing the importance of a middle layer
no waaaay this is so awesome
for sure, it was just a general rule of thumb I found with bandwidths in the gb range
100% agree
time for the unholy quaternity of automated chttp tests with lua-runner, gluatest, and httpserver