W3C home > Mailing lists > Public > public-ws-addressing@w3.org > January 2005

Re: NEW ISSUE: EPR comparison rule doesn't support Web services gateways/routers

From: Mark Baker <distobj@acm.org>
Date: Thu, 27 Jan 2005 00:41:05 -0500
To: "public-ws-addressing@w3.org" <public-ws-addressing@w3.org>
Message-ID: <20050127054105.GJ17671@markbaker.ca>

Hi Rich,

On Wed, Jan 26, 2005 at 11:37:54PM -0500, Rich Salz wrote:
> > Paco, can you not just use a different URI instead of different
> > RefParams in order to distinguish between multiple services behind a
> > gateway?  If not, why?
> 
> Because people want to only expose a single endpoint, and then
> have their infrastructure dispatch or route based on things like message
> content.

That would be just fine by me, since layering is maintained.  What I
understood Paco to want is to be able to *identify* services behind a
gateway using RefParams in the request message.  That would break
layering.

> There several reasons for doing this; one of the most compelling
> is that they do not want to expose *anything* about their internal
> deployment details.  It avoids giving attackers any information.

Right.  Enforcing layering would avoid giving out that info, while
breaking layering would reveal it.

FWIW, URIs vs. RefPs doesn't change the layering, but the reason I asked
the question above was to find out if the "gateway" could be a proxy,
in which case there's no layering issue since a proxy works on behalf
of the sender.

Mark.
-- 
Mark Baker.   Ottawa, Ontario, CANADA.        http://www.markbaker.ca
Received on Thursday, 27 January 2005 05:41:01 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 2 June 2009 18:35:01 GMT