Re: RFC: draft-brown-device-stock-ua-00.txt

I am not certain I understand the question, but I'll answer with where the
'situational' part could come in.  The two simplest are:

1) Origin outputs device specific content and uses the intermediary simply
to accelerate and/or cache
2) Origin serve generic content and the intermediary performs the
appropriate adaptation

I the latter example, the origin dose not necessarily need to know the
device details and removing or changing the header may be appropriate.  In
the former the header is less important to the intermediary though they
still may need to for caching the content appropriately of so desired by
the origin.


On 11/13/12 7:30 PM, "Eitan Adler" <> wrote:

>On 13 November 2012 17:26, Ludin, Stephen <> wrote:
>> As an intermediary/surrogate, this makes a lot of sense.  I can see the
>> specific behavior required being very situational.
>When might I ask, would Akamai want to take action based on a browser
>the user not using and may not even be installed?
>Eitan Adler

Received on Thursday, 15 November 2012 00:04:31 UTC