What platform would you run Quetoo on if it was on Steam?:

HTTP downloading

September 04, 2008 - 07:30am

I've setup a Quake2World server and it runs fine except for HTTP downloading. I've read the documentation on it but I didn't get it done for some reason. I've seen several servers where it works, so the problem's most likely not related to my client settings.

Some details on what I've done so far:

Here's what I've got in my server config file.

q2w@airrocket:~$ grep download q2wsrv.cfg
set sv_downloadurl "http://www.airrocket.net/q2wrepo/"
set sv_udpdownload "0"

The repo exists at that URL as you can see and has a pak and a map file in the proper subdirectories. Both of them get downloaded via UDP instead of HTTP though when I connect without local copies of those maps -- which takes ages (> 15 mins for the pak file in there!).

What did I mess up?

Thanks, spirit

NOTE: The config file gets parsed by the server, the other settings in there work.

...and while I'm at it: Would be cool to have a key that aborts the download (and thus the connection to the server). I have to kill the q2w process every time I connect and a file gets downloaded via UDP 'cause I don't want to wait 15 minutes for it to finish.

September 22, 2008 - 09:13am

That config looks correct to me. Any update on this? Is it still failing for you?


September 24, 2008 - 16:19pm

Yes, it's still messed up. Strange, I've got an r1q2 repo running on the same server that works well and the q2w repo stuff works for all the other q2w servers. And setting it up really doesn't seem that complicated.

Guess something weird is going on, maybe with my Apache 2 installation. I'll leave it for now and have another look at the config files and stuff in a few days.


September 25, 2008 - 09:09am

The only thing I can think of is that your HTTP server is returning some non-200 status code, and perhaps the Q2W HTTP code is too brittle to cope with it? Maybe have a look at cl_http.c and see if that sounds possible.



Meh, I just checked and your server's returning status 200. Why don't you open a ticket in Trac and I'll dig into this one soon-ish. Attach your actual server.cfg to the Trac ticket.