W3C home > Mailing lists > Public > www-jigsaw@w3.org > November to December 1996

Re: PostableResource problems

From: Craig Brozefsky <cosmo@dobie.ebs.net>
Date: Fri, 15 Nov 1996 11:47:32 -0600 (CST)
To: www-jigsaw@w3.org
Message-ID: <Pine.LNX.3.91.961115114113.12573A-100000@dobie.ebs.net>
On Thu, 14 Nov 1996, Steve wrote:

> > Document not found
> > The document http:blagblah is indexed but not available
> > The server is misconfigured
> I believe this has to do with the PostableResource not converting GETs to 
> POSTs properly. I'm guessing what you did is added your resource and then 
> typed in

Yah.  Since PostableResource is sub-classed from FileResource you end up 
with a call to FileResource.get() if you do not have a query string on 
the end of the URL since PostableResource.get() checks 
request.hasState('query') and fails thus invoking super.get(request) 
calling the get() method of FileResource which of course is misconfigured 
since i never assigned a filename to it.

> Where 'whatever' is literally that - any characters. The GET will then be
> properly converted to a POST and everything will work wonderfully.	
> Does anyone know another way around this?

I assigned a filename ot it, reluctantly.

I am trying to make a resource that will take information like a CGI 
program, meaning it will allow me to use PATHINFO to pass along 
information to the resource as well as QUERYSTRING.  I am kinda perplexed 
about where I should start.  I need a resource that will snarf up the 
request even if it's not the last "filename" in the path of the URL.
Received on Friday, 15 November 1996 12:46:16 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:41:21 UTC