[2.1] Can I change HTTP headers sent by a generator?

All, I realize that Cocoon 2.1 is now unsupported, but I suspect this is something that hasn't changed a lot since then. I have a sitemap with a generator: http://internal/service/foo; /> Is there a way I can add custom HTTP headers to the request that will be made to

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

Greg, On 3/31/22 12:17, Christopher Schultz wrote: Greg, On 3/29/22 13:41, gelo1234 wrote: Have you also tried HTMLT or XHTMLT Serializers? Default HTMLSerializer cannot handle some unicode characters: https://issues.apache.org/jira/browse/SLING-5973?attachmentOrder=asc Hmm. Are the HTMLT

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

Greg, On 3/31/22 12:13, Christopher Schultz wrote: On 3/29/22 13:37, gelo1234 wrote: Hello Chris, I think you will not get any icon-type character on output without using proper font rendering - like Emoji support? Emoji might not be supported by default in Cocoon. This isn't a font

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

sg61629.html> Greetings, Greg wt., 29 mar 2022 o 18:36 Christopher Schultz mailto:ch...@christopherschultz.net>> napisał(a): Cédric, On 3/29/22 12:06, Cédric Damioli wrote: > Could you provide more details ? > How is your XML

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

/msg61629.html I read that, and was hopeful that 2.1.13 would resolve this issue, but it hasn't. Hmm... strangely, the X-Cocoon-Version header still says 2.1.11. Perhaps I didn't upgrade properly... Thanks, -chris wt., 29 mar 2022 o 18:36 Christopher Schultz mailto:ch

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

ing whatever Cocoon uses natively. For example, I don't throw-in Jackson or StaX or whatever other options there are. For "markers", you may use labels on your sitemap steps associated with a cocoon view. Yeah, that sound familiar. Thanks, -chris Le 29/03/2022 à 18:36, Christopher Sc

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

Cédric, On 3/29/22 12:06, Cédric Damioli wrote: Could you provide more details ? How is your XML processed before outputting the wrong UTF-8 sequence ? It's somewhat straightforward: https://source/; />

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

with no HTML entities. I've double-checked, and the source XML contains the flag as a single multi-byte character, served as UTF-8. Any ideas for how to get this working? I'm sure I could put together a trivial test-case. Thanks, -chris On 10/30/18 12:18, Christopher Schultz wrote: All

Re: using cocoon 2.1 in the long-term, security concerns

Vincent, On 7/19/21 08:03, Vincent Neyt wrote: Hi Cocoon users, I'd like to ask your opinion on the long-term security risks of running Cocoon on a server. The colleague responsible for the servers at my university is inquiring if the software I'm using for my website is up to date and is

Re: Cocoon 2.1.11 problem with JDK release versions above 255

Vincent, On 6/30/21 11:24, Vincent Neyt wrote: Hi all, thank you very much for all your reactions. I just found time to try Nico Verwer's suggestion, and that worked perfectly! It seems it was the very old version of icu4j.jar that caused the problem. As Nico suggested I exchanged it for

Re: Getting UTF-16 encoding on dynamic content regardless of output content type

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, Some additional information at the end. On 10/30/18 11:58, Christopher Schultz wrote: > All, > > I'm attempting to do everything with UTF-8 in Cocoon 2.1.11. I have > a servlet generating XML in UTF-8 encoding and I hav

Getting UTF-16 encoding on dynamic content regardless of output content type

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm attempting to do everything with UTF-8 in Cocoon 2.1.11. I have a servlet generating XML in UTF-8 encoding and I have a pipeline with a few transforms in it, ultimately serializing to XHTML. If I have a Unicode character in the XML which

Replacable parameters in HTML in I18nTransformer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I'm using the i18n transformer to localize my XSLTs. I have a somewhat odd use-case where I'd like to have some (final) text that looks like this: Please click here to do something interesting. The url in the link needs to have some

Re: Trouble switching locales with i18ntransformer

global" After fixing those two issues, I'm getting the expected text in the expected language. Apologies for the noise, and thanks for the help! Thanks, - -chris > Le 09/01/2018 à 17:34, Christopher Schultz a écrit : All, > > I have an I18NTranformer configured and elements in my

Re: Trouble switching locales with i18ntransformer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, On 1/9/18 11:34 AM, Christopher Schultz wrote: > All, > > I have an I18NTranformer configured and elements in my > stylesheets and everything is working for the default locale. But > changing locales doesn't seem to be wo

Trouble switching locales with i18ntransformer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I have an I18NTranformer configured and elements in my stylesheets and everything is working for the default locale. But changing locales doesn't seem to be working for me. I think I must be missing something. I'm using Cocoon 2.1.11.

Re: [2.1] Overzealous escaping of high Unicode code points

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Greg, On 6/20/17 4:11 PM, Christopher Schultz wrote: > Greg, > > On 6/8/17 2:17 PM, gelo1234 wrote: >> Chris, > >> Even with C3 (cocoon 3.0 beta) unless you specify optional >> encoding in your Serializer config, yo

Re: [2.1] Overzealous escaping of high Unicode code points

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Greg, On 6/8/17 2:17 PM, gelo1234 wrote: > Chris, > > Even with C3 (cocoon 3.0 beta) unless you specify optional encoding > in your Serializer config, you fallback to default UTF-8: > >

[2.1] Overzealous escaping of high Unicode code points

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I've been testing my application for use with high Unicode code points such as emoji like  which is this one: http://www.fileformat.info/info/unicode/char/1F60D/index.htm My application and database can handle this code point, but Cocoon

Re: Handling errors retrieving a for

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Javier On 6/1/16 3:19 PM, Javier Puerto wrote: > Hi Christopher, > > I more used to version 2.2 but it should be the same. By you > description I think about creating a new pipeline with a matcher to > handle the external request with a specific

Re: Handling errors retrieving a for

her were in the same pipeline? Speaking of caching, I'd prefer for the "remote-handler" matcher to re-try pretty regularly. Do matchers cache at all under normal circumstances? I've never bothered attempting to configure any caching in Cocoon before. Thanks, - -chris >

Handling errors retrieving a for

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, Using Cocoon 2.1, I've got an aggregate generator like this: http://remote-server/baz.xml; /> ... There are times when "remote-server" is not available and I'd like to basically include nothing at that location

Re: [2.1] Non-trivial uses of i18n transformer

Francesco, On 5/23/16 9:58 AM, Francesco Chicchiriccò wrote: > On 23/05/2016 15:55, Christopher Schultz wrote: >> Marc, >> >> On 5/23/16 9:39 AM, Marc Salvetti wrote: >> > Try something like this > > I18n-attr="title"/> >> >> &g

Re: [2.1] Non-trivial uses of i18n transformer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Marc, On 5/23/16 9:39 AM, Marc Salvetti wrote: > Try something like this I18n-attr="title"/> > > That's by memory but should find the exact syntax in the doc Yep, this totally works. Since I'm on a roll, how about this: function

Re: [2.1] Non-trivial uses of i18n transformer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Francesco, On 5/23/16 9:41 AM, Francesco Chicchiriccò wrote: > On 23/05/2016 15:39, Marc Salvetti wrote: >>> Hi Chris, > > Try something like this title="some.catalogue:some.text" I18n-attr="title"/> > > That's by > memory but should find the exact

[2.1] Non-trivial uses of i18n transformer

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I'm finally getting around to internationalizing the XSLT-based parts of my application, and I'm running into a problem with non-trivial uses of in a template. Here's an excellent example of the kind of thing I'm having trouble with. I have a

Re: [2.1] cinclude using a pipeline as a generator source

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Nico, On 5/10/16 4:35 AM, Nico Verwer wrote: > On 7-5-2016 15:10, Christopher Schultz wrote: >> On 5/7/16 7:38 AM, warrell harries wrote: >>>> cocoon:// is understood as standard >>> Awesome. I was hoping it would be som

Re: [2.1] cinclude using a pipeline as a generator source

Warrell, On 5/7/16 8:58 AM, Christopher Schultz wrote: > Warrell, > > Thanks for the quick reply! > > On 5/7/16 7:38 AM, warrell harries wrote: >> cocoon:// is understood as standard > > Awesome. I was hoping it would be something simple like that. > >&g

Re: [2.1] cinclude using a pipeline as a generator source

I get this error: org.apache.cocoon.ResourceNotFoundException: No pipeline matched request: ./foo/bar/baz.html;jsessionid=97079C2DC1E19B20F2BEB8303AECF74E I'm vry close. Just have to fix the speling, evidently ;) Thanks, -chris > On 7 May 2016 12:12, "Christopher Schultz" <ch...@

[2.1] cinclude using a pipeline as a generator source

All, I've got a Cocoon setup with a pipeline whose transformer contains something like this: https://my-app/get-some-data; /> Now, the URL included there is actually coming from Cocoon, and actually I have a certificate that Java doesn't trust, so I get errors about PKI certification paths. I

Re: Help needed moving from 2.1.11

Peter, On 1/6/16 11:59 AM, Flynn, Peter wrote: > On 06/01/16 14:18, Christopher Schultz wrote: > >> Moving from Tomcat 5 on (presumably) an older Java to a newer version >> should not be difficult at all. Is there a reason to move to Tomcat 6 >> and not all the way

Re: Help needed moving from 2.1.11

Peter, On 1/6/16 6:33 AM, Flynn, Peter wrote: > ...I think. > > I have an existing Cocoon service running 2.1.11 under Tomcat5 and > Apache in CentOS5 on a very old server, and I now have a new server > running CentOS6, Apache2, and Tomcat6 that I want to migrate to, but I > am held up by my

Adding EXSLT functions

-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 All, I've been successfully using EXSLT functions -- specifically, the date-and-time functions (http://exslt.org/date/index.html) -- for some years now and I was interested in using the seconds function. It turns out that the seconds function is

Re: Getting the value of the browser selector

Peter, On Dec 19, 2013, at 4:24, Peter Flynn pfl...@ucc.ie wrote: Let me try again in a shorter post :-) 1. Has anyone ever used the browser selector? 2. Can it be used to pass the *value* to a transformation as a parameter without resorting to map:when, instead of just doing

Re: Trouble with disable-output-escaping

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robby, On 11/13/12 1:41 PM, Robby Pelssers wrote: Allright... You should reminder this tip. It will only work if you do this in the very last transformer right before calling the serializer. Okay, since I have a number of transform operations,

Trouble with disable-output-escaping

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I'm running Cocoon 2.1.11 on Oracle Java 1.6.0_26. I'm using the default Xalan 2.7.1 XSLT processor. All examples are roughly mocked-up from a much more complicated configuration so I apologize if there are typos, etc. -- I hand-typed this

Re: Cocoon 2.1 web application base path

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andy, On 5/16/12 12:36 PM, Andy Stevens wrote: Hi Bob, Assuming you have the request input module in your cocoon.xconf, then you can pass the context path into an xsl:param (or otherwise use in the sitemap) with e.g. map:transform

Re: Using I18NTransformer with Dynamic Locales

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Cédric, On 12/2/11 4:04 PM, Cédric Damioli wrote: Le 01/12/2011 17:49, Christopher Schultz a écrit : All, I'd like to start using the I18NTransformer so I can localize the output of my XSLTs. We have what I believe to be a somewhat unique

Re: AW: revelet not repsonding

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jürgen, On 1/6/12 5:14 AM, Ehms, Jürgen wrote: With the first mapping /* all is going to Cocoon. Put it in last place. That's not how url-pattern matching works: longest-match always wins. /* is the default mapping, which takes lowest precedence.

Using I18NTransformer with Dynamic Locales

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I'd like to start using the I18NTransformer so I can localize the output of my XSLTs. We have what I believe to be a somewhat unique situation with regard to the actual source of the locale information. Here goes: We have Cocoon set up as a

Re: Setting URLConnection User-Agent String

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Warren, Resurrecting an old thread: I hadn't noticed your reply back in March. On 3/1/2011 5:46 AM, warrell harries wrote: It doesn't make any difference - it's plain old HTTP despite the jargon :) Of course. If you have already seen this

Re: tomcat memory issue

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, On 5/25/2011 11:14 AM, DAVIGNON Andre (Responsable du PANDOC) - SG/SPSSI/CPII/DONP/PANDOC wrote: As far as I know, it is the same Tomcat engine that you run either on a 32 or 64 bits JVM. Only the JVM matters. If your JVM runs in 64 bits,

Re: Setting URLConnection User-Agent String

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Warrell, On 2/28/2011 6:41 AM, warrell harries wrote: Please see recent discussion regarding proxying to another server. In brief, I usually deploy a custom transformer based on the web service proxy transformer but setting the user agent header

Setting URLConnection User-Agent String

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I'm using Cocoon 2.1.11 with some pipelines that fetch data from another webapp via Apache httpd which logs the requests with the User-Agent being Java/whatever. I'm wondering if Cocoon offers the ability to tweak the User-Agent string that is

Re: i18n cookies storing path

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Johan, On 1/7/2011 5:45 AM, Johan Cwiklinski wrote: Le 07/01/2011 11:24, Laurent Medioni a écrit : Strictly match, at the beginning of the pipeline, (or /, I never remember...) and call the LocaleAction only there. Then end the matcher just

Re: Encoding

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Laurent, On 12/17/2010 11:25 AM, Laurent Medioni wrote: Have a look at http://wiki.apache.org/tomcat/FAQ/CharacterEncoding I think the comment you refer to tries to say that if no charset/encoding is set when producing a response then assume the

Re: Deploying a Cocoon 2.2 webapp in Tomcat 6.0.20

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Florian, On 10/4/2010 7:01 AM, Florian Schmitt wrote: i'm quite new regarding cocoon 2.2 and i'm stuck trying to deploy a Cocoon 2.2 webapp in Tomcat 6.0.20. Ok. I followed those steps to create a minimal webapp : Good. If you have a WAR file,

Re: System upgrade and now Cocoon is escaping tabs/entities.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 J, On 9/29/2010 1:10 AM, . . wrote: #a9 should be a copyright symbol if you're using ASCII. I suspect that #a9 is being used instead of a newline (0xa) followed by a tab (0x9). Actually it was a typo on my part. It's using #9; :( *oops* Yeah,

Re: form encoding issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Ron, On 9/29/2010 5:43 AM, Ron Van den Branden wrote: There is stated that apparently (and counter-intuitively, IMO), 'request parameters are always decoded using ISO-8859-1 ', and that consequently 'container_encoding should always be

Re: form encoding issues

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, On 9/29/2010 7:05 AM, Thomas Markus wrote: hi, that arabic character should fail with latin1. we see a difference between jetty and tomcat (6.0). tomcat follows specs (see Andre's mail) and uses iso per default. you can switch

Re: System upgrade and now Cocoon is escaping tabs/entities.

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 J, On 9/28/2010 10:09 AM, . . wrote: Our original application components were: NetBSD 3.0.3 with Suse 9.x Linux compatibility layer. Sun JDK 1.4.26 Tomcat 5.0.23 Cocoon 2.1.6 As part of the upgrade we switched to: Centos 5.3 Sun JDK

Re: Cocoon 2.2 PUT HTTP request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/22/2010 3:36 AM, Andre Juffer wrote: Try confirming (say, with LiveHttpHeaders) that the PUT is being redirected by the server. This is what I see with LiveHttpHeaders: http://localhost:/equipment/ POST /equipment/

Re: Cocoon 2.2 PUT HTTP request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, (Is everyone on the list named Andre? :) On 9/21/2010 9:10 AM, Andre Juffer wrote: There is still one other issue to be solved. In the case of a PUT request (or any other HTTP request for that matter), my understanding is that I should be

Re: RESTful applications

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/21/2010 6:22 AM, Andre Juffer wrote: I found this (for Tomcat 5)

Re: Cocoon 2.2 PUT HTTP request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/21/2010 2:04 PM, Andre Juffer wrote: On 09/21/2010 07:38 PM, Christopher Schultz wrote: I find the Cocoon documentation very difficult to navigate. Can you point me to the documentation for calling javascript functions? All I could

Re: Cocoon 2.2 PUT HTTP request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/21/2010 3:15 PM, Andre Juffer wrote: This provides an overview of the cocoon.request methods: http://cocoon.apache.org/2.2/blocks/flowscript/1.0/1383_1_1.html Okay, this looks like a HttpServletRequest object with a few more methods

Re: Cocoon 2.2 PUT HTTP request

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/21/2010 4:26 PM, Andre Juffer wrote: I got it working now. It is really in the details. I always relied upon a PUT request like http://localhost:/equipment expecting to see the request method set to PUT. In fact, it was

Re: RESTful applications

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/20/2010 6:34 AM, Andre Juffer wrote: Could it be true that Jetty (the one that comes with cocoon is 6.1.7, a rather old one) is actually not supporting the getParameters() family of methods when the HTTP request method is PUT? This

Re: RESTful applications

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andre, On 9/20/2010 3:06 PM, Andre Juffer wrote: The source of my problem is therefore clear. Absolutely. PUT and POST have somewhat different meanings to RESTful applications and I intend to stick to that. On the tomcat list, it was indeed also

Re: [C3] How to/where to disable certificate check accessing HTTPS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrei, On 9/10/2010 4:35 PM, Andrei Lunjov wrote: One more thing was needed: HostnameVerifier verifyEverything = new HostnameVerifier() { public boolean verify(String hostname, SSLSession session) { return true; } };

Re: wrong encoding used when opening xml file with encoding utf-8

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robby, On 9/13/2010 8:31 AM, Robby Pelssers wrote: I'm generating an html table using Chinese characters and i set the encoding and mimetype as follows: var response = cocoon.response;

Re: [C3] How to/where to disable certificate check accessing HTTPS

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Andrei, On 9/10/2010 4:05 AM, Andrei Lunjov wrote: Hi Jos, I just try to do: map:generate src=https://asite.with.invalid.cert/some/resource/ And sun.net.www.protocol.https.HttpsURLConnectionImpl if I remember right throws an exception.

Re: argument type mismatch when using fn:replace

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Robby, On 8/17/2010 6:29 AM, Robby Pelssers wrote: Here are some notes on how to add the saxon transformer in attached screenshot. No attachment; only one of those stupid MS winmail.dat files :( - -chris -BEGIN PGP SIGNATURE- Version:

Re: argument type mismatch when using fn:replace

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 André, On 8/6/2010 4:39 PM, florent andré wrote: Good news, you don't have to switch all your cocoon app from xalan to saxon !! Thanks for the tip! It's great to know that Xalan and Saxon can be used in the same Cocoon instance. That will

Re: argument type mismatch when using fn:replace

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Thomas, On 8/4/2010 5:09 PM, Thomas Ernest wrote: I remember having this problem, when I used the same version of Cocoon one year ago. I'm not 100% sure, but I mean fn:replace is a function belonging to XPath 2.0 [1] and Cocoon 2.1.11 integrates

Re: argument type mismatch when using fn:replace

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, On 8/5/2010 12:57 PM, Christopher Schultz wrote: On 8/4/2010 5:09 PM, Thomas Ernest wrote: I remember having this problem, when I used the same version of Cocoon one year ago. I'm not 100% sure, but I mean fn:replace is a function belonging

Re: argument type mismatch when using fn:replace

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Mark, On 8/5/2010 1:32 PM, Mark Eggers wrote: I haven't used Cocoon in quite a while, but I remember that you can use Saxon instead of Xalan. A quick google search brings up the following old blog entry from Vadim:

argument type mismatch when using fn:replace

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 All, I've been using Cocoon 2.1.11 successfully for quite some time, and I'm trying to add new capabilities to our product. I'm tripping-up when trying to use fn:replace with a regular expression. I'm on Debian Lenny with Debian's package-managed