My favorites | Sign in
Project Logo
                
New issue | Search
for
| Advanced search | Search tips
Issue 6: The "type" parameter is not working
1 person starred this issue and may be notified of changes. Back to list
Status:  Accepted
Owner:  tony.hammond
Type-Defect
Priority-Medium


Sign in to add a comment
 
Reported by tony.hammond, Mar 20, 2008
The "type" parameter does not seem to work.

So,

...?index=2

does work

whereas

...?type=URL nor ...?type=url

does not. Suggest anyway that type values be made *case insensitive*.
Comment 2 by christopher.townson, Mar 20, 2008
the value supplied as the type parameter needs to match the string value for one of
the enumeration net.handle.servlet.HandleRecordType which are currently:

HS_ADMIN, HS_ALIAS, HS_NA_DELEGATE, HS_PRIMARY, HS_SERV, HS_SITE, HS_VLIST

This could be made case insensitive, but 'url' is not currently a member of the
enumeration. There are therefore two possible errors here:

1. The enumeration is incomplete. We need to add 'url'
2. The type parameter is mapped to the wrong set of possible values, so we need to
establish what the possible values are and implement them.

Comment 3 by tony.hammond, Mar 20, 2008
I believe it should be a free case-insensitive string comparison against the string 
contained in the type field. That would allow for any user types to be matched.

(Currently there are four registered user types: URL, URN, EMAIL, DESC. But we should
allow for any unregistered types, e.g. XMP. :)

We are not trying to enforce type restriction here. That would only be appropriate at
handleregistration - and not even then. User types (also unregistered) are allowed.
Comment 4 by christopher.townson, Apr 12, 2008
Okay - that shouldn't be a problem. I'll look into it and see if I can get this fixed
this weekend.
Status: Accepted
Sign in to add a comment

Hosted by Google Code