Is FileGenerator doing URL encoding?

2003-01-23 Thread Rui Leal
Hello !! I'm using cocoon 2.0.4 to develop a prototype of a small webapp which has Tamino XML Server as data repository. Tamino allows me to pass a HTTP xquery (using x-machine) to the database.. like this http://databasehost/tamino/databasename/col?_xquery=input()/* So .. with cocoon i'm

RE: URL Encoding

2002-12-20 Thread Volker Schneider
- From: Ludovic de Beaurepaire [mailto:[EMAIL PROTECTED]] Sent: Donnerstag, 19. Dezember 2002 10:39 To: [EMAIL PROTECTED] Subject: URL Encoding Hi All, In an Action i want to encode an URL on the HttpResponse to have the session Id on this URL. url

Re: URL Encoding

2002-12-20 Thread Ludovic de Beaurepaire
] Sent: Friday, December 20, 2002 11:10 AM Subject: RE: URL Encoding Hi Ludovic, you can have problems because the URL encoder probably does encode the leading semicolon and the equals symbol of the URL if you use URL rewriting. Maybe you have to write a short method which avoids encoding

URL Encoding

2002-12-19 Thread Ludovic de Beaurepaire
Hi All, In an Action i want to encode an URL on the HttpResponse to have the session Id on this URL. url = ((org.apache.cocoon.environment.http.HttpResponse)(ObjectModelHelper.getResp onse(objectModel))).encodeURL(url); But my URL is not encoded. I don't find where to configure if encoding is

RE: Cocoon 2, Batik, URL encoding, bug? (long-ish, sorry)

2002-05-06 Thread Vadim Gritsenko
is... it doesn't work with non-ASCII letters. E.g. if my text contains German Umlauts (vowels a,o,u with two dots on them), the resulting button displays two arbitrary characters. I suspect what goes bad is the URL encoding (i.e. encoding 'special' characters as %xx escape sequences). I think

Cocoon 2, Batik, URL encoding, bug? (long-ish, sorry)

2002-05-05 Thread Daniel Vogelheim
(vowels a,o,u with two dots on them), the resulting button displays two arbitrary characters. I suspect what goes bad is the URL encoding (i.e. encoding 'special' characters as %xx escape sequences). I think at some point the string gets converted into URLs using UTF-8, but elsewhere gets decoded