W3C home > Mailing lists > Public > www-jigsaw@w3.org > January to February 1997


From: Bob Barter <Bob.Barter@quickmail.llnl.gov>
Date: 22 Jan 1997 09:51:26 -0800
Message-ID: <n1358195434.99486@quickmail.llnl.gov>
To: "Jigsaw Mail List" <www-jigsaw@www10.w3.org>
                      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:
    brings up the form.
6) Filling out the form and selecting "submit" sends the information to the
7) The resource replies and Netscape displays the information along with
    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
    which - I think - gets interpreted as a GET without a query string
    which - I think - causes the dreaded "...indexed but not available..."
    which - I think - causes Jigsaw to remove the resource.

Is there a way to protect against loosing the resource to this kind of action?
Received on Wednesday, 22 January 1997 12:57:43 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:25:30 UTC