Re: post request
Subject: Re: post request
From: firstname.lastname@example.org (Marco Framba)
Date: Thu, 4 Apr 1996 16:11:13 -0800 (PST)
From email@example.com Thu Apr 4 19: 12:08 1996
In-Reply-To: <199604042002.PAA03464@anansi.w3.org> from "Henrik Frystyk Nielsen" at Apr 4, 96 03:02:12 pm
Phone: (415) 614-2209 - Fax: (415) 614-0200
X-Mailer: ELM [version 2.4 PL23]
Henrik Frystyk writes:
> Yes, in fact this is the reason why you an anchor for the source (your local
> and one for the destination (the reponse sent by the cgi script) When you link
> together two anchors you create a link object with the link relationship and
> to be used.
> Normally, you should be able to get the resonse without problems - have you
> the verbose output - it may be that the response simply goes down a black hole.
I tryed to run:
w3c -v -post -dest http://foo/getfile.cgi file:/.login
and verified that after the library write the file ".login"
to the socket, it does not even try to read the response
sent by the system "foo". Even if you specify a destination
that does not exist the call-back routine terminate_handler()
receive a status of HT_LOADED.