Re: PostableResource

        Reply to:   RE>PostableResource

Anselm,

I can understand your confusion with Step 5 being the same as Step 8.  My
error.

Step 5 is correct:
5) Using Netscape 3.0, the URL:
    http://....:8001/Test/test_survey.html
    brings up the form.

Steps 7 and 8 should show the URL of the resource, not the html file as
indicated in my original e-mail.  Steps 7 and 8 should be:
7) The resource replies and Netscape displays the information along with
     http://....:8001/User/test_survey
    as the URL

8) If I place the cursor in the URL line and hit return, then the browser
tries to access
    http://....:8001/User/test_survey
    which - I think - gets interpreted as a GET without a query string
    which - I think - causes the dreaded "...indexed but not available..."
message
    which - I think - causes Jigsaw to remove the resource.

At your suggestion, I set the extensible flag to false for the
DirectoryResource: User.  It looks as though setting the flag to false
prevents the resource from being deleted when the "...indexed but not
available..." condition occurs.

I can live with this since the users should not be directly accessing the
resource anyway.

Thanks for your help,
Bob
--------------------------------------
Date: 1/22/97 10:24 AM
To: Bob Barter
From: Anselm Baird-Smith
Bob Barter writes:
 >                       Subject:                              Time:  9:06 AM
 >   OFFICE MEMO         PostableResource                      Date:  1/22/97
 > 
 > OK, I think I'm getting the hang of PostableResources (always a risky
 > assumption -- but what the heck).
 > 
 > I have read the 20 messages in the mail archive having to do with
 > PostableResource and have installed and run examples by Mark Lubin
 > (JigsawSurvey) and by Anselm Baird-Smith (ReverseString) -- my thanks to
both
 > of you.  I think I'm OK as long as I stay in the shallow end of the pool.
 > 
 > I think I understand the GET/query string/ConvertGet issue.  However, it
looks
 > as though a user could inadvertently blow the resource away under the
 > following conditions:
 > 
 > 1) I have a resource installed as: ..../User/test_survey
 > 2) I have the ConvertGet flag set to: true
 > 3) I have a html file: /Test/test_survey.html
 > 4) The html file contains:
 >     <FORM METHOD="POST" ACTION="http://....:8001/User/test_survey">
 > 5) Using Netscape 3.0, the URL:
 >     http://....:8001/Test/test_survey.html
 >     brings up the form.
 > 6) Filling out the form and selecting "submit" sends the information to the
 > resource
 > 7) The resource replies and Netscape displays the information along with
 >      http://....:8001/Test/test_survey.html
 >     as the URL
 > 
 > <<< So far - nothing very exciting >>> 
 > 
 > 8) If I place the cursor in the URL line and hit return, then the browser
 > tries to access
 >     http://....:8001/Test/test_survey.html
 >     which - I think - gets interpreted as a GET without a query string
 >     which - I think - causes the dreaded "...indexed but not available..."
 > message
 >     which - I think - causes Jigsaw to remove the resource.
 > 
 > Is there a way to protect against loosing the resource to this kind of
action?

Set the container directory extensible flag to false, but that's not
really needed in your case:

step 5 says:

 > 5) Using Netscape 3.0, the URL:
 >     http://....:8001/Test/test_survey.html
 >     brings up the form.

and latter on, steps 8:

 > 8) If I place the cursor in the URL line and hit return, then the browser
 > tries to access
 >     http://....:8001/Test/test_survey.html
      
cause problems, I can't see the difference between these two calls (at
least wrt what happens in the server ?) I think I understand your
situation, but I would guess there is a config error somewehere.

Anselm.

Received on Wednesday, 22 January 1997 14:38:50 UTC