On 18/04/07, Tomas Restrepo <[EMAIL PROTECTED]> wrote:
Hi Robert,
> I *think* that both sides ignore a leading / [I should really check
> this]...
> but that client might add one (for luck) on sending where one is not
> present. As others have pointed out, AMQP0-8 (and indeed AMQP 0-9)
> mandates
> a leading /, which is a waste of a byte. Those of us on the AMQP
> working
> group should probably aim for a clarification / simplification of the
> definition of vhost.
>
> Currently it is defined as of domain "path" which means:
>
> Must start with a slash "/" and continue with path names separated by
> slashes. A
> path name consists of any combination of at least one of [A-Za-z0-9]
> plus zero or more of [._+!=:].
Ahh, OK, I see. What confused me was that going through the spec, the
validation regexp for the virtual-host name doesn't mandate that (it's
currently "^[a-zA-Z0-9/-_]+$").
It does seem pretty weird to model a virtual-host name as a path, though,
but maybe that's just me. It would seem then, that the bug is in the .NET
client which doesn't ensure the virtual host name is sent with a "/" if the
user doesn't specify one.
It is worse than that.. the spec can't agree if it is a virtual-path
or virtual-host. If it were a path then the '/' would make sence but
there is a large section comparing it to Apache httpd virtualhosts.
Tomas Restrepo
http://www.winterdom.com/weblog/
--
Martin Ritchie
