[Gnu-arch-users] bug? archive created via "ftp" method not usable via "http" method

[Miles Bader]

I created a mirror archive of my main archive "address@hidden"  using the
following command:

   tla make-archive --signed --listing --mirror address@hidden address@hidden 
ftp://USER:address@hidden/arch/address@hidden

Then I mirrored some stuff to it:

   $ tla archive-mirror address@hidden address@hidden tla-tools
   * mirroring address@hidden to address@hidden with limit tla-tools
   * creating version address@hidden/tla-tools--devo--0
   ** adding revision tla-tools--devo--0--base-0
   ** adding revision tla-tools--devo--0--patch-1
   $ tla archive-mirror address@hidden address@hidden snogray
   * mirroring address@hidden to address@hidden with limit snogray
   * creating version address@hidden/snogray--devo--0
   ** adding revision snogray--devo--0--base-0
   ** adding revision snogray--devo--0--patch-1
   ** adding revision snogray--devo--0--patch-2
   ** adding revision snogray--devo--0--patch-3
   ** adding revision snogray--devo--0--patch-4

Abrowse works fine via ftp:

   address@hidden
     snogray
       snogray--devo
         snogray--devo--0
           base-0 .. patch-4

     tla-tools
       tla-tools--devo
         tla-tools--devo--0
           base-0 .. patch-1

Now, because this ftp dir is my ISP's web upload area, I should be able
to see the same files via http, and in a browser, I can indeed see stuff
with no problem.

However, if I try to access the same archive using tla using the "http"
access method, it doesn't work:

   $ tla register-archive address@hidden 
http://www2.gol.com/users/USER/arch/address@hidden
   $ strace -s1000 tla abrowse address@hidden
   ...
   write(3, "GET /users/USER/arch/address@hidden/.listing HTTP/1.1\r\nHost: 
www2.gol.com\r\nUser-Agent: arch-client/0.1 neon/0.24.7\r\nConnection: 
TE\r\nTE: trailers\r\n\r\n", 147) = 147
   select(4, [3], NULL, NULL, {120, 0})    = 1 (in [3], left {119, 800000})
   read(3, "HTTP/1.1 200 OK\r\nDate: Sun, 29 Apr 2007 05:54:00 GMT\r\nServer: 
Apache/2.2.3 (Debian)\r\nLast-Modified: Sun, 29 Apr 2007 05:43:13 GMT\r\nETag: 
\"5d6c7-32-42f39d8283e40\"\r\nAccept-Ranges: bytes\r\nContent-Length: 
50\r\nContent-Type: 
text/plain\r\n\r\n=meta-info\r\nsnogray--devo--0\r\ntla-tools--devo--0\r\n", 
4096) = 283
   write(4, "=meta-info\r\nsnogray--devo--0\r\ntla-tools--devo--0\r\n", 50) = 
50  
   lseek(4, 0, SEEK_SET)                   = 0
   fstat(4, {st_mode=S_IFREG, st_size=50, ...}) = 0
   read(4, "=meta-info\r\nsnogray--devo--0\r\ntla-tools--devo--0\r\n", 50) = 50
   close(4)                                = 0
   write(2, "Failed to access file \'", 23) = 23
   write(2, ".archive-version", 16)        = 16
   write(2, "\'\n", 2)                     = 2
   write(2, "Could not determine archive format, guessing to be tla 1.0\n", 59) 
= 59
   ...

The resulting error messages are:

   Failed to access file '.archive-version'
   Could not determine archive format, guessing to be tla 1.0

Given that the following sequence of events happens:

  (1) It reads the top-level .listing file (which works)

  (2) It immediately gives the failed-to-access-.archive-version error,
      without obviously _trying_ to access it

I'm guessing that it actually expects ".archive-version" to be part of
.listing, but it's not (so "failed to access" here really means "didn't
find").  Is this a bug of the ftp method?  _Should_ it be putting
".archive-version" (etc) in .listing?

Thanks,

-Miles