Content on linux/unix web servers is case sensitive, content on win32 webservers is not.
For the BSP this can be complex since the map name "mapNaMe.bsp" as entered on the server console or in the mapcycle defines the bsp name that will be requested from the URL (so on linux/unix servers the case must match) then the content that is defined in the .res file and within the BSP must match as well, so a sound name that is "sound.WAV" requires that exact name and case on the linux/unix webserver too. Having a different case for the content in the .res file (from the actual content in the BSP) may cause the content to be downloaded (attempted) a second time, always important to have all content name/case match everywhere. One thing to be aware of though, if content with a space or other special character is not available, the client may display a truncated name in console for the failed content. For example, hldm server, + linux web server which does _not_ have this piece of content available: "sound/music/don't_worry_be_happy.wav" the webserver will flag the correct name: [Tue Nov 8 10:38:02 2005] [error] [client xxx.xxx.xxx.xxx] File does not exist: valve/sound/music/don't_worry_be_happy.wav but the client will display a message that the failed download is: Error: server failed to transmit file 'sound/music/don' (client will properly d/l the file if it is available). Win32 HTTP servers just send it all regardless of case, assuming its available. So in summary (so it all works regardless): 1. server must have a .res file for the BSP locally and on the http server 2. content names in .res file must match content names within the BSP including case 3. content names on http server must match content names within the BSP including case 4. mapcycle name (or map as typed in console) must have the same case as the mapname on the http server If you are running any addon mod (like MANI or adminmod) that can force additional content down, be sure to disable this since if that content is not on your http server it will cause an additional connect/reconnect by the client to the http server as well. Any content not available on your http server won't be downloaded so there should be no bandwidth hit regardless of the number of failed attempts. ----- Original Message ----- From: "Chris K" <[EMAIL PROTECTED]> To: <hlds@list.valvesoftware.com> Sent: Tuesday, November 08, 2005 9:14 AM Subject: [hlds] sv_downloadurl issue
I've noticed and had a few complaint's of an issue where resources are redownloaded over again upon reconnecting. I have seen this myself on my client and am looking for more insight. My issue might have been a matter of case. My client had a few uppercase files and my isp host had lowercase files (identical files otherwise). Now windows is not case sensitive and Unix is, which may or may not be the problem. Once I deleted the files and reconnected they came down one last time and all has been well (I did not try renaming them). Anyone else have any story's/fixes to tell regarding files repeatedly downloading? My fear is that I could be unnecessarily running out the bandwidth clock on my host.
_______________________________________________ To unsubscribe, edit your list preferences, or view the list archives, please visit: http://list.valvesoftware.com/mailman/listinfo/hlds
