On Sat, 2002-05-04 at 06:07, [EMAIL PROTECTED] wrote: > Hi Bruno, > > Thanks for participating in my post > > Well what I really wanted was just > as Cocoon is able to detect that > the request is coming from Nokia, > UPSDK or an Ericsson R380 device and > accordingly delivers WAP content, it > should be able to detect that the > request is coming from Kannel, and similarly > deliver WAP content (please refer to > the snip that I have provided) > > The reason is simple, it was a time-consuming > job to add each and every phone model > in the cocoon.properties. > > While reading the cocoon.properties I > came to the conclusion that Cocoon was > recognizing the agent- from which the request > came- via a particular service name or the > headers that the agent was issuing: > > browser.1=wap=Nokia > browser.2=wap=UP > browser.3=wap=R380 > > Similarly I was trying to find out > what can be done to make Cocoon deliver > WAP content to Kannel. Should I include > the bearerbox-host variable value in > cocoon.properties or the headers which > Kannel issues (X-WAP-Gteway). > > Your input has brought a new dimension > to the whole issue. > > Can you elaborate a bit further? What are > the other variables that should appear be > defined in the service group (apart from name)? > The Kannel documentation does not contain any > mention of this service group variables. > > Thanks once again. > > SNODX >
When you receive a request from a mobile, you should read an header with Accept: text/vnd.wap.wml, .... You can rely on that to see if it's wap enabled Besides, Kannel sends an User-Agent: <mobile name and version> (this one was broken some days ago) and two aditional headers: Via: WAP/1.1 <hostname> (Kannel/cvs-20020502). X-WAP-Gateway: Kannel/cvs-20020502
