W3C home > Mailing lists > Public > www-lib@w3.org > July to September 1996

4.1b3a HTRule callback wish, HTParse port problem

From: Bill Rizzi <rizzi@softserv.com>
Date: Tue, 27 Aug 1996 11:08:26 -0700
Message-ID: <3223399A.44A7@softserv.com>
To: www-lib@w3.org
Just a couple of things I'd like to see ...

* Ability to add user-defined rules (other than map/pass)

	Similar to "gateway" and "proxy" rules, I'd like to add my own rules,
along with a function to call on a match.  For a library with callbacks to 
spare, I'm surprised that libwww doesn't have one here (HTRule).  Just a 
nit: the file name is HTRules.[ch] but the functions are called HTRule_*.

* End hostname port parsing on an invalid port character

	Not sure about this one, as I'm not positive that only digits are 
allowed in a port number.  If this is the case, then it would be great if 
HTParse would stop parsing the port number when/if it hits a non-digit.

	I came across this one in MiniServ while creating an HTTP request to 
be passed to the Harvest cache, which looks for a request like this:

	GET http://xxx.yyy.zzz/dir/file

	So the URL to be sent to the cache looks like this:

	http://harvest.cache:port/http://xxx.yyy.zzz/dir/file

	The problem is that HTParse() generates:

	GET /http://xxx.yyy.zzz/dir/dir/file

	When I try:

	http://harvest.cache:porthttp://xxx.yyy.zzz/dir/file

	HTParse picks up `port`http: as part of the host name and generates:

	GET //xxx.yyy.zzz/dir/file

	If HTParse() stopped port parsing on the 'h' of "http://xxx", all 
would be well.

	But perhaps I'm missing something?

	Z

-- 
Bill Rizzi	rizzi@softserv.com			Software Services
    Z		http://www.softserv.com/~rizzi		Santa Barbara, CA
Received on Tuesday, 27 August 1996 14:07:36 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 23 April 2007 18:18:26 GMT