RE: OPES protocol, pre-draft

see inline,

abbie


> -----Original Message-----
> From: Alex Rousskov [mailto:rousskov(_at_)measurement-factory(_dot_)com] 
> Sent: Wednesday, February 19, 2003 3:37 PM
> To: ietf-openproxy(_at_)imc(_dot_)org
> Subject: Re: OPES protocol, pre-draft
>
>
>
>
> On Wed, 19 Feb 2003, jfcm wrote:
>
> > Let assume that www.w3c.com says to redirect calls to 
> www.w3.org and 
> > that www.w3.org says to redirect calls to www.w3c.com. What happens?
> A loop detection code at the second hop would see its own 
> Via: header already in the HTTP headers of the request and 
> would not forward the request further, responding with an 
> error. This is how redirections (and loop detection) are 
> supposed to work today.
yes, in theory.

> This issue is not directly related to OPES except that OPES 
> callout server might participate in loop detection by adding 
> its own Via headers (or application-specific equivalent). I 
> do not know whether the current requirement/architecture 
> drafts consider callout server a "proxy hop" on the 
> application protocol path. They probably should.

I think so, this should help in tracing/notification.

abbie

SNIP


abbie