Here are my headers :

Host:products.mobilescope.com
X-Widget-Id: devtest-mobilescope-afp-journal-une
User-Agent: Yahoo-Mobile/1.0 (CrossPoint; 1.0) Accept:
application/x-onesearch+xml,application/x-ywidget+xml,application/x-ysnippet+xml\
,application/atom+xml,application/rss+xml,image/*

Accept-Charset: utf-8
Accept-Language: fr
Geo-Country: fr
X-Carrier: frorange
X-Client: j2me; Go; 3.0.4302; YHOO
X-Device: 3988
Via: HTTP/1.1 proxy51.mobile.re3.yahoo.com



--- In yhoomobiledevelopers@yahoogroups.com, Chris Stivers
<cstivers1978@...> wrote:
>
> You should be receiving the UA and the phone's make and model.
> If not, can you forward all the headers sent to you?
>
>
> ----- Original Message ----
> From: mobilescope <mobilescope@...>
> To: yhoomobiledevelopers@yahoogroups.com
> Sent: Wednesday, September 24, 2008 9:10:03 AM
> Subject: [yhoomobiledevelopers] Re: X-Device Header
>
>
> Hi,
>
> My question is then : why does Yahoo! (you) send third parties servers
> this (apparently useless) x-device header ?
>
> Do you still confirm that we have no way of matching x-device header
> with a phone model or user agent ?
>
> Why not forwarding the UA ?
>
> --
> Mathieu
>
> --- In yhoomobiledeveloper s@yahoogroups. com, Chris Stivers
> <cstivers1978@ ...> wrote:
> >
> > Most
> > people in the world do not have the capabilities to process the
> > User-Agent header to figure out what type of device is calling them.
> > User-Agent
> > header alone sometimes does not correctly identify a calling device,
> > such as the case of Opera Mobile/Mini web browsers which use their own
> > User-Agent. The Blueprint platform processes these headers and
> detects the device being used, and forwards the detected device to the
> widgets via the X-Device header. Information about the actual client
> on the device being used (Web Browser, Y!Go, etc) is sent via the
> X-Client header.
> >
> > Yahoo! Mobile has a catalog of (mobile) devices,
> > called Device Catalog, which is also the piece responsible for
> matching the headers to a device id. This device id is the first
> number you see in the X-Device
> > header, which is followed by the Make and Model of the device.
> > The Device Catalog also provides additional device attributes such
> as screen and media capabilities. Currently, Device Catalog is not
> open to the public, only Yahoo! mobile
> > is able query Device Catalog. We are working on plans to open Device
> > Catalog to the world, but it will not likely happen this year. In
> the mean time, we have been selecting device attributes to trickle
> down to the widgets via an X-Device-Attributes header.
> >
> > X-Device-User- Agent/X-Original -User-Agent are not related, and only
> provides information the original User-Agent of the device. This
> header is usually sent
> > when the device is accessing a web page via content
> transformation/ transcoding service such as those used by Yahoo!,
> Google and others. This is used because the User-Agent header contains
> the User-Agent of the content transformation/ transcoding service, not
> the device.
> >
> >
> >
> >
> > ----- Original Message ----
> > From: iamhermiony <no_reply@yahoogroup s.com>
> > To: yhoomobiledeveloper s@yahoogroups. com
> > Sent: Thursday, August 28, 2008 8:21:50 AM
> > Subject: [yhoomobiledevelope rs] Re: X-Device Header
> >
> >
> > ็ำ็HELLO
> > I DON'T KNOW TO MUCH FOR THE X-DEVICE BUT I FOUND SOME KNOWLEDGE ON
> > THE INTERNET. MAY BE THIS WEB
> > http://dev.mobi/ blog/x-device- user-agent- header-appearing
-requests ,
> > IT WILL HELP YOU TO FINE THE
> > ANSWER .
> > GOOD LUCK
> > ^_^
> > --- In yhoomobiledeveloper s@yahoogroups. com, "munteanubog"
> > <munteanubog@ ...> wrote:
> > >
> > > Hi,
> > >
> > > I noticed that in every request from Yahoo server it is sent a
> X-Device
> > > header with a number.
> > > How does Yahoo obtains this number? Is it a standard or just
> something
> > > implemented by Yahoo?
> > >
> > > I'm asking this because, as a content provider I would like to
> identify
> > > what is the device making the requests. Do you know a way to do
this?
> > >
> > > Thank you.
> > >
> > ็ำ้
> >
>