cocoon-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Oscar Trigueiros <>
Subject RE: sendRedirect 1.8 and 1.8.1+ differences...
Date Wed, 21 Feb 2001 10:55:59 GMT
          I'm learning to use Cocoon, but i do now someting about Wap.
          The Nokia browser don't seen to suporte the HTTP redirect headers,
the best way to solve this problem that we found is using
          the card element attribute onenterforward, someting like this:
             <card onenterforward="href"> 
    This results in the redirection to the url defined in the atribute and
works for all browsers because

    it is standart WML1.1.

    But i have some questions of my one that im looking for am answer before
starting using Cocoon im one prodution


         How do i change,update or edit XML or database data using Cocoon
and on one web page  

 -----Original Message-----
From: Saravanan Bellan []
Sent: terça-feira, 20 de Fevereiro de 2001 22:52
To: ''
Subject: RE: sendRedirect 1.8 and 1.8.1+ differences...

We have started using RequestDispatcher.forward for all redirects in our
site because of  weird behaviour of some WAP devices.

-----Original Message-----
From: Paul Nock []
Sent: Tuesday, February 20, 2001 2:37 PM
Subject: sendRedirect 1.8 and 1.8.1+ differences...

Have some very weird behavior with cocoon 1.8/1.8.1 and the Nokia WAP
toolkit and HTTP Redirects - I'm using Ulrich Mayring's auth taglib.
With cocoon 1.8, everything works fine.
With cocoon 1.8.1 (and later) the redirect stuff for authentication does not
work with Nokia's WAP toolkit.
Now, I'm sure the problem is ultimately with Nokia's toolkit - but that's
not open-source so I can't fix it ;-) Fact is SOMETHING about the redirect
generated by Cocoon 1.8.1 is different, and for the life of me I can't see
what it is.  When I "GET" the url through telnet, nothing obvious stands
out, and I can make the Nokia toolkit redirect with my own non-cocoon cgi
stuff.  Any other browser works fine.  If I look in the cocoon log file, I
can see the redirect happening - accessing a protected URL, then redirecting
to the login.xml page, but on the simulator itself I just get a blank
Weirder still is that the Nokia Toolkit has a config option
"allow-http-redirect", or something like it with a default of FALSE.  This
would obviously explain why the 1.8.1 redirect does NOT work - because it's
disabled.  But in that case, why does the 1.8 redirect work?
Why do I care? The Nokia "allow-http-redirect" option is a WAP gateway
setting, so I can't rely on it being set the way I want for Nokia browsers
to get to my site. I would like my 1.8.2 Cocoon installation to redirect
Nokia browsers the same way that 1.8 does.
Paul Nock

View raw message