Launchbase Syringe/Ares updating problems

[Renegade]

D has just run that thing again for the enjoyment of our logs, and the server shows the following happening:

Code:

1.      xx.yy.zz.aa - - [03/May/2009:11:04:59 +0200] "GET /rss.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&sc=0&isdir=1 HTTP/1.1" 206 2655 "-" "Microsoft URL Control - 6.00.8862"
2.      xx.yy.zz.aa - - [03/May/2009:11:05:01 +0200] "GET /rss.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&sc=0&isdir=1 HTTP/1.1" 206 2655 "-" "Microsoft URL Control - 6.00.8862"
3.      xx.yy.zz.aa - - [03/May/2009:11:05:03 +0200] "GET /dl.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&isdir=1 HTTP/1.1" 200 14600 "-" "Microsoft URL Control - 6.00.8862"
4.      xx.yy.zz.aa - - [03/May/2009:11:05:06 +0200] "GET /dl.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&isdir=1 HTTP/1.1" 200 79933 "-" "Microsoft URL Control - 6.00.8862"
5.      xx.yy.zz.aa - - [03/May/2009:11:05:26 +0200] "GET /rss.php?repname=Ares&path=%2Freleases%2Fmsvc%2F&rev=0&sc=0&isdir=1 HTTP/1.1" 200 8930 "-" "Microsoft URL Control - 6.00.8862"

Code:

1.      xx.yy.zz.aa - - [03/May/2009:11:29:55 +0200] "GET /rss.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&sc=0&isdir=1 HTTP/1.1" 206 2655 "-" "Microsoft URL Control - 6.00.8862"
2.      xx.yy.zz.aa - - [03/May/2009:11:29:58 +0200] "GET /rss.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&sc=0&isdir=1 HTTP/1.1" 206 2655 "-" "Microsoft URL Control - 6.00.8862"
3.      xx.yy.zz.aa - - [03/May/2009:11:30:00 +0200] "GET /dl.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&isdir=1 HTTP/1.1" 200 14600 "-" "Microsoft URL Control - 6.00.8862"
4.      xx.yy.zz.aa - - [03/May/2009:11:30:03 +0200] "GET /dl.php?repname=Syringe&path=%2Freleases%2Fmsvc%2F&rev=0&isdir=1 HTTP/1.1" 200 79932 "-" "Microsoft URL Control - 6.00.8862"
5.      xx.yy.zz.aa- - [03/May/2009:11:30:25 +0200] "GET /rss.php?repname=Ares&path=%2Freleases%2Fmsvc%2F&rev=0&sc=0&isdir=1 HTTP/1.1" 200 8930 "-" "Microsoft URL Control - 6.00.8862"

I have checked all three links shown, and they're all fine, specifically:

• The Syringe download link does deliver the full directory content including a 114176 byte Syringe.exe
  
• The Ares RSS definitely works
  

So whatever problems you're having are not server-side.

An interesting thing D pointed out is that, not only are you querying each url twice, but you are getting a differently-sized response in line 4 compared to 3, and I noticed you're getting an almost-equal, but off-by-one-byte response for the two 4s.
Theory:
Is it possible that LB behaves this way:

1. Query RSS
   
2. Query RSS
   
3. Start Download 1
   
4. Create File 1
   
5. Start Download 2
   
6. Create File 2
   
7. Detect Download (1) is done
   
8. End Downloads (1 & 2) because Download (1) is done
   
9. Extract File 2
   
10. Fail
    

Maybe it chooses File 2 because it's newer, or because it overwrote File 1, point is: Maybe it's trying to download twice, aborts both downloads when the first one is done, but trying to extract the partial file?
Does the issue persist when the number of downloads is reduced to one?


As for Ares's RSS - interesting is that you're getting code 206 for the Syringe RSS (Partial Content), but 200 for the Ares one...maybe MS URL Control doesn't expect that?

206 Partial Content
The server is serving only part of the resource due to a range header sent by the client. This is used by tools like wget to enable resuming of interrupted downloads, or split a download into multiple simultaneous streams.

Since the Syringe one is the one being read fine, it can't be that 206 startles it...and 200 is "OK", after all, and used by the dl.php ones as well, so there should be no problem with that. Only thing I can think of is that the switch between 206 and 200 confuses it, somehow.

(In any case, it'd be nice if you queried each item only once...think of the server )