Re: Cannot access Cocoon WAP page

2002-12-10 Thread Skip Carter

Costantino,

 but unfortunately that did not fix the problem. In fact, I have the same
 problem if I try to access hello.html, for example, with the mobile device
 (which should be no problem).
 Do you have any idea?

   Try this site with the mobile browser:  http://www.caphnet.com/

   This is the one that we created with the modifications that I described.  
Let me know if it
   works with that browser.  Let me know what happens.




Skip



-- 
 Dr. Everett (Skip) Carter  Phone: 831-641-0645 FAX:  831-641-0647
 Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED]
 1340 Munras Ave., Suite 314WWW: http://www.taygeta.com
 Monterey, CA. 93940












-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: Cannot access Cocoon WAP page

2002-12-10 Thread Costantino Sertorio
Hi Skip,
I can access your site without problem with my mobile - but unfortunately
not yet mine (http://titao.homelinux.org:8080/cocoon/hello.wml)...
I also tried every possible combination with
http://webcab.de/cgi-bin/fetchpage.cgi, checking the result in the core.log
file.
I am really puzzled, I don't understand what can be wrong.

Can you see something wrong in this log file (from an access test with the
mobile)?
Or can you suggest any other test that I can do?

REMOTE HOST: 138.188.101.64
REMOTE ADDRESS: 138.188.101.64
REMOTE USER: null
REQUEST SESSION ID: null
REQUEST PREFERRED LOCALE: it
SERVER HOST: titao.homelinux.org
SERVER PORT: 8080

METHOD: GET
CONTENT LENGTH: -1
PROTOCOL: HTTP/1.1
SCHEME: http
AUTH TYPE: null

CURRENT ACTIVE REQUESTS: 1
REQUEST PARAMETERS:

HEADER PARAMETERS:

PARAM: 'host' VALUES: '[titao.homelinux.org:8080]'
PARAM: 'accept' VALUES: '[application/vnd.wap.wmlc;Type=4365,
application/vnd.wap.wmlc;Type=4360, application/vnd.wap.wmlc;Type=1108,
application/vnd.wap.wmlc;Level=1.3, application/vnd.wap.wmlc,
application/vnd.wap.wmlscriptc, application/vnd.wap.multipart.related,
application/vnd.wap.multipart.mixed, application/x-up-device,
application/vnd.phonecom.mmc-wbxml;Type=4364,
application/vnd.phonecom.mmc-wbxml, application/vnd.phonecom.im,
application/octet-stream, application/vnd.openwave.pp,
application/vnd.wap.sic, application/vnd.wap.slc, application/vnd.wap.coc,
application/vnd.uplanet.bearer-choice-wbxml, application/vnd.uplanet.signal,
application/vnd.uplanet.cacheop-wbxml, application/vnd.uplanet.alert-wbxml,
image/vnd.wap.wbmp, image/bmp, image/x-MS-bmp, audio/midi, audio/x-midi,
audio/mid, text/x-vCalendar, text/x-vCard, text/plain,
application/x-mmc.wallpaper;type=image/bmp;size=2000;gray=1;w=101;h=64,
application/x-mmc.ringtone;type=audio/midi;size=2000;voices=1,
application/x-mmc.title;charset=us-ascii;size=30,
image/bmp,image/vnd.wap.wbmp,application/vnd.uplanet.alert,application/x-up-
alert,application/vnd.uplanet.bearer-choice,application/vnd.uplanet.cacheop,
application/x-up-cacheop,application/vnd.phonecom.mmc-xml,text/x-wap.wml,tex
t/vnd.wap.wml,text/x-hdml,text/html,text/vnd.wap.wmlscript,text/vnd.wap.co,t
ext/vnd.wap.si,text/vnd.wap.sl, */*]'
PARAM: 'accept-charset' VALUES: '[utf-8, UTF-8, *]'
PARAM: 'accept-language' VALUES: '[it]'
PARAM: 'encoding-version' VALUES: '[1.3, 10 1.3]'
PARAM: 'user-agent' VALUES: '[SIE-ME45/23 UP.Browser/5.0.2.2 (GUI)
UP.Link/5.1.1.4]'
PARAM: 'x-up-devcap-charset' VALUES: '[utf-8]'
PARAM: 'x-up-devcap-gui' VALUES: '[1]'
PARAM: 'x-up-devcap-iscolor' VALUES: '[0]'
PARAM: 'x-up-devcap-max-pdu' VALUES: '[2800]'
PARAM: 'x-up-devcap-numsoftkeys' VALUES: '[2]'
PARAM: 'x-up-uplink' VALUES: '[spwapgw1p.swissptt.ch]'
PARAM: 'x-up-wappush-secure' VALUES: '[www.openwave.com:9003/pap]'
PARAM: 'x-up-wappush-unsecure' VALUES: '[www.openwave.com:9002/pap]'
PARAM: 'connection' VALUES: '[close]'

Thanks,

Costantino

- Original Message -
From: Skip Carter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Sent: Tuesday, December 10, 2002 7:50 PM
Subject: Re: Cannot access Cocoon WAP page



 Costantino,

  but unfortunately that did not fix the problem. In fact, I have the same
  problem if I try to access hello.html, for example, with the mobile
device
  (which should be no problem).
  Do you have any idea?

Try this site with the mobile browser:  http://www.caphnet.com/

This is the one that we created with the modifications that I
described.
 Let me know if it
works with that browser.  Let me know what happens.




 Skip



 --
  Dr. Everett (Skip) Carter  Phone: 831-641-0645 FAX:  831-641-0647
  Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED]
  1340 Munras Ave., Suite 314WWW: http://www.taygeta.com
  Monterey, CA. 93940













-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: Cannot access Cocoon WAP page

2002-12-10 Thread Skip Carter

Costantino,

 I can access your site without problem with my mobile - but unfortunately
 not yet mine (http://titao.homelinux.org:8080/cocoon/hello.wml)...
 I also tried every possible combination with
 http://webcab.de/cgi-bin/fetchpage.cgi, checking the result in the core.log
 file.
 I am really puzzled, I don't understand what can be wrong.
 
 Can you see something wrong in this log file (from an access test with the
 mobile)?

   Unfortunately at the moment, my mobile phone browser returns 'Service Not 
Available'
   so I can't do it from there with the phone.  My WML browser on my Palm PDA 
works with
   your site works just fine.


 Or can you suggest any other test that I can do?

If you try using netcat (nc) to access the pages you can see the problem:

simulating a proper WML browser (say Nokia):

$ nc www.caphnet.com 80
GET /index.xml HTTP/1.0
User-Agent: Nokia


returns:

HTTP/1.1 200 OK
Date: Tue, 10 Dec 2002 23:34:30 GMT
Server: Apache
Content-Type: text/vnd.wap.wml
X-Cocoon-Version: 2.0.2
Vary: User-Agent
Connection: close

!DOCTYPE wml PUBLIC -//WAPFORUM//DTD WML 1.1//EN 
http://www.wapforum.org/DTD/wml_1.1.xml;
wml xmlns:xsp=http://www.apache.org/1999/XSP/Core;card id=CaphNet Main 
Menu title=CaphNet Main Menua title=Company href=/company/index.xml
About CaphNet/abr/a title=Browser href=/browser/index.xmlCaphNet 
Family of Freedom Browser Software Platforms/abr/a title=Partnerships 
href=/partnerships/index.xmlJoin Us/abr/p/
The CaphNet site contents are written entirely in XML.

The entire site can be viewed with any HTML or WML Browser.
/card/wml


And for the UP browser:


$ nc www.caphnet.com 80
GET /index.xml HTTP/1.0
User-Agent: UP

returns:

HTTP/1.1 200 OK
Date: Tue, 10 Dec 2002 23:33:54 GMT
Server: Apache
Content-Type: text/html
X-Cocoon-Version: 2.0.2
Vary: User-Agent
Connection: close

wml xmlns:xsp=http://www.apache.org/1999/XSP/Core;
card id=CaphNet Main Menu title=CaphNet Main Menu
a title=Company href=/company/index.xmlAbout CaphNet/a
br
a title=Browser href=/browser/index.xmlCaphNet Family of Freedom Browser 
Software Platforms/a
br
a title=Partnerships href=/partnerships/index.xmlJoin Us/a
br
p/p
The CaphNet site contents are written entirely in XML.

The entire site can be viewed with any HTML or WML Browser.
/card
/wml



Note that !DOCTYPE is missing in the second version (I found out by 
experimenting, that the Content-Type field
does not really matter for the UP browser).  When I go to your WML page, it 
always returns !DOCTYPE.  If you
arrange your sitemap so that !DOCTYPE is never sent for the UP user agent, 
then you should be okay.  Are
you sure that the changes that you tried earlier accomplished that ?



Skip





-- 
 Dr. Everett (Skip) Carter  Phone: 831-641-0645 FAX:  831-641-0647
 Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED]
 1340 Munras Ave., Suite 314WWW: http://www.taygeta.com
 Monterey, CA. 93940












-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: Cannot access Cocoon WAP page

2002-12-09 Thread Skip Carter

 I am having a problem while trying to access the sample hello.wml sample =
 page of Cocoon (I am running Apache Tomcat with Cocoon 2.0.3 on a =
 Windows 2000 system) with a mobile phone.
 The WAP browser waits a few seconds and then answers:
 500: Web service problem:
 Please contact service provider.
 If I then select Details, I read:
 1500: Could not connect to site.
 
 I have tried with a number of WAP emulators and it works perfectly; it =
 also works if I save the WML page and let the webserver serve it =
 directly
 (I also tried using different telecom providers with no success).

 Anyone has any ideas of the reason why this behaviour can happen?

 PARAM: 'user-agent' VALUES: '[SIE-ME45/23 UP.Browser/5.0.2.2 (GUI) UP.Link/5.1.1.4]'

The problem that you are having is because the UP.Browser does not like the 
DOCTYPE prologue
in the page that is being generated/sent.

You can make a quick fix by making your pipeline use map:serialize 
type=html/
instead of map:serialize type=wml/  for wap user agents.

In production, we use a more general solution of introducing a new browser 
agent in the sitemap
selectors section:

   browser name=wapx useragent=UP/!-- broken WML browser, does not 
like the DOCTYPE prologue --


and then testing for a wapx browser in the pipeline:

map:select type=browser
 map:when test=wap
 map:transform src=stylesheets/{level}_wml.xsl /
 map:serialize type=wml/
 /map:when
 map:when test=wapx
 map:transform src=stylesheets/{level}_wml.xsl /
 map:serialize type=html/
 /map:when
 map:otherwise
 map:transform src=stylesheets/{level}_html.xsl /
 map:serialize type=html/
 /map:otherwise
/map:select


this gives us the ability to handle proper WML browsers as well as the broken 
one.



Skip



-- 
 Dr. Everett (Skip) Carter  Phone: 831-641-0645 FAX:  831-641-0647
 Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED]
 1340 Munras Ave., Suite 314WWW: http://www.taygeta.com
 Monterey, CA. 93940












-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]




Re: Cannot access Cocoon WAP page

2002-12-09 Thread Costantino Sertorio
Hi Skip and thank you,
but unfortunately that did not fix the problem. In fact, I have the same
problem if I try to access hello.html, for example, with the mobile device
(which should be no problem).
Do you have any idea?

Costantino



- Original Message -
From: Skip Carter [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, December 10, 2002 1:13 AM
Subject: Re: Cannot access Cocoon WAP page



  I am having a problem while trying to access the sample hello.wml sample
=
  page of Cocoon (I am running Apache Tomcat with Cocoon 2.0.3 on a =
  Windows 2000 system) with a mobile phone.
  The WAP browser waits a few seconds and then answers:
  500: Web service problem:
  Please contact service provider.
  If I then select Details, I read:
  1500: Could not connect to site.
 
  I have tried with a number of WAP emulators and it works perfectly; it =
  also works if I save the WML page and let the webserver serve it =
  directly
  (I also tried using different telecom providers with no success).

  Anyone has any ideas of the reason why this behaviour can happen?

  PARAM: 'user-agent' VALUES: '[SIE-ME45/23 UP.Browser/5.0.2.2 (GUI)
UP.Link/5.1.1.4]'

 The problem that you are having is because the UP.Browser does not like
the
 DOCTYPE prologue
 in the page that is being generated/sent.

 You can make a quick fix by making your pipeline use map:serialize
 type=html/
 instead of map:serialize type=wml/  for wap user agents.

 In production, we use a more general solution of introducing a new browser
 agent in the sitemap
 selectors section:

browser name=wapx useragent=UP/!-- broken WML browser, does
not
 like the DOCTYPE prologue --


 and then testing for a wapx browser in the pipeline:

 map:select type=browser
  map:when test=wap
  map:transform src=stylesheets/{level}_wml.xsl /
  map:serialize type=wml/
  /map:when
  map:when test=wapx
  map:transform src=stylesheets/{level}_wml.xsl /
  map:serialize type=html/
  /map:when
  map:otherwise
  map:transform src=stylesheets/{level}_html.xsl /
  map:serialize type=html/
  /map:otherwise
 /map:select


 this gives us the ability to handle proper WML browsers as well as the
broken
 one.



 Skip



 --
  Dr. Everett (Skip) Carter  Phone: 831-641-0645 FAX:  831-641-0647
  Taygeta Scientific Inc.INTERNET: [EMAIL PROTECTED]
  1340 Munras Ave., Suite 314WWW: http://www.taygeta.com
  Monterey, CA. 93940












 -
 Please check that your question  has not already been answered in the
 FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail:   [EMAIL PROTECTED]



-
Please check that your question  has not already been answered in the
FAQ before posting. http://xml.apache.org/cocoon/faq/index.html

To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail:   [EMAIL PROTECTED]