Re: Tracking client-applications using User-Agent

If the request hits a cache your origin server isn't going to see the
request so how would that work?

I think I would just stick to doing auth via the auth header. But I might
be missing something?

Cheers,
M
On 3 Apr 2013 09:46, "Jan Algermissen" <[email protected]> wrote:

> **
>
>
> Hi,
>
> suppose, you expose a REST-API and want to keep track clients which you
> gave access to the API. Each client is given a client ID.
>
> Straight-forward solution would be to use the Authentication (think OAuth)
> header to extract the client ID.
>
> However, suppose there are some resource you do not want to protect to
> enable public caching.
>
> What about asking the client developers to put the client ID in the
> User-Agent header. Yes, they would not have to, but let's suppose they are
> closely enough associated to be reliable enough. If this occasionally
> slips, that's no big deal. It is for monitoring purposes only. No
> payment-per-ID or throttling involved.
>
> Do you have any thoughts or experiences doing something similar?
>
> Jan
>  
>