W3C home > Mailing lists > Public > www-jigsaw@w3.org > March to April 1999

Re: PUT doesn't PUT for me

From: Yves Lafon <ylafon@w3.org>
Date: Mon, 12 Apr 1999 10:54:03 +0200 (MET DST)
To: "Burleigh, Frank" <burleigh@indiana.edu>
cc: "'www-jigsaw@w3.org'" <www-jigsaw@w3.org>
Message-ID: <Pine.GSO.4.10.9904121042330.10372-100000@tarantula.inria.fr>
On Sun, 11 Apr 1999, Burleigh, Frank wrote:

> Hello.  I've just begun to work with Jigsaw 2.02 under OS/2.  Since it seems
> to work quite well, I thought I'd put it to a particular use.  Netscape 4.5x
> has the notion of roaming profiles.  These could be quite useful for people
> like me who use a bunch of PCs.  When it starts, Netscape will look on an
> http server directory (with authentication) for a user profile, and on exit,
> it will PUT these files back to the server.
> 
> So I created in JS a DirectoryResource like this:
> + ProfileSpace
>    + HTTPFrame (Putable, Browseable, etc., are TRUE; I've left method blank
> and also put them all in)
>       + GenericAuthFilter

Not only the Container should be putable, but also the resources!
To do that, the best way is to add a new indexer (ContentTypeIndexer is
the most adapted to do this work).
It is described at http://www.w3.org/Jigsaw/Doc/User/publication.html
Note, content types like text/* (text:*) can be matched, to help things.
The frame of every resource you put under this one should have the flag
putable set to "true" if you want it to be putable

> 
> I browsed to this directory to test authentication, and found that it works
> ok.  Then I turned on NS' roaming profiles and told NS to look in
> ProfileSpace for profiles.
> 
> In this scenario, NS' first job on start is to hit ProfileSpace with a PUT
> of a file called WRITETEST.  At that time it uses your login and password.
> I can't get past this point, as NS says there's a network error, and that
> the server isn't responding.  Once I've got Netscape going I *can*
> authenticate to ProfileSpace, and I can see the file called WRITETEST.  But
> WRITETEST isn't actually on the http server's file system.  And when I click
> WRITETEST in the browser I get back the message from JS that there is no
> such file, and that the server is misconfigured.
> 
> The log shows:
> - PUT WRITETEST with result 401
> - DELETE WRITETEST with result 405
> - PUT WRITETEST with result 405
> - DELETE WRITETEST with result 405
> 
> I have some guesses about what's wrong:
> - I haven't correctly told JS that it can PUT into ProfileSpace (Methods on
> the GenericAuthFilter do include PUT)
> - JS doesn't know what kind of file WRITETEST is, so it doesn't know *how*
> to put it on the file system.
> - There's some other connection between a PUT and the file system that I
> don't know about.
> 
> Also, the SERVER.PROPS file has TRACE set to true but I don't get anything
> in the traces file.
> 
> Frank Burleigh
> Indiana University School of Law-Bloomington
> burleigh@indiana.edu; voice 812-855-9170
> 
> 
> 

      /\          - Yves Lafon - World Wide Web Consortium - 
  /\ /  \        Architecture Domain - Jigsaw Activity Leader
 /  \    \/\    
/    \   /  \   http://www.w3.org/People/Lafon - ylafon@w3.org    
Received on Monday, 12 April 1999 04:54:13 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 9 April 2012 12:13:29 GMT