How do we know whether a service URI is available (relatedquestion)

Drummond Reed drummond.reed at
Fri Aug 25 05:16:42 UTC 2006

+1. In fact the HTTP HEAD request may be the lightest-weight mechanism
proposed yet.

Mike Mell: would this not be even easier than appending the (+active) query
parameter? And avoid the issues about requiring append="qxri"?


-----Original Message-----
From: yadis-bounces at [mailto:yadis-bounces at]
On Behalf Of Johannes Ernst
Sent: Thursday, August 24, 2006 9:14 PM
To: OpenID Discussion
Cc: iss-comment at; i-broker-discuss at
Subject: Re: How do we know whether a service URI is available

Can I ask for a virtual show of hands (-1/0/+1) of people who think  
that we should have some kind of very lightweight "ping" for OpenID  
service endpoints in time for the OpenID 2.0 spec, preferably using  
an approach that works for other kinds of services, too, or not?

I was actually thinking of an HTTP HEAD on the service endpoint,  
looking for an HTTP error code (or TCP timeout) or an HTTP success  
code. (or a redirect code, in which case the new service endpoint  
should be pinged instead).

But regardless of how we'd specify that ping ... should we have such  
a thing? Or not? Or "not now"?



Johannes Ernst
NetMesh Inc.

More information about the yadis mailing list