[Helma-user] jetty upgrade broke UTF-8 URLs

[Hannes Wallnoefer]

2007/3/27, Juerg Lehni <juerg at scratchdisk.com>:
> I guess I will face the same problem as soon as I update.
>
> I am very interested in a fix of this. Shouldn't we get the Jetty
> people involved instead of just downgrading again?

If you have the time and dedication to do that, that would certainly
be the best solution (in addition to just downgrade with Helma for the
time being). I doubt the Jetty folks will be keen to make bold changes
to version 4 (it's tagged deprecated), but maybe it has some effect on
the current version, too.

hannes

> Jürg
>
> On 27 Mar 2007, at 10:37, Hannes Wallnoefer wrote:
>
> > Hi Michi,
> >
> > downgrading is ok with me. Let's see how far we need to downgrade in
> > order to fix this. Any idea?
> >
> > hannes
> >
> > 2007/3/27, Michael Platzer <michael.platzer at knallgrau.at>:
> >> Hi,
> >>
> >> The recent upgrade from Jetty 4.2.22 to 4.2.27 in Helma HEAD broke
> >> our
> >> beautiful utf-8 URLs [1]
> >>
> >> Until now I was able to handle UTF-8 escaped URLs with mod_jk with
> >> the
> >> following settings:
> >>   charset = UTF-8
> >> and
> >>  JkOptions +ForwardURIEscaped
> >>
> >> After I upgraded twoday.net to the most recent Helma 1.6.x snapshot,
> >> users complained that they can not access topics with Umlauts anymore
> >> [2]. As soon as I downgraded Jetty to 4.2.22 again, everything worked
> >> fine again.
> >>
> >> I could also reproduce this bevahiour in a local setup with mod_jk. I
> >> also tried to the other available JkOptions
> >> (+ForwardURICompatUnparsed,
> >> +ForwardURICompat), but with no success. I am not able to serve utf-8
> >> escaped URLs with mod_jk and Jetty 4.2.27. What puzzles me, is
> >> that the
> >> Jetty ChangeLog does not mention anything related to UTF-8 (see
> >> below).
> >>
> >> Should we consider downgrading Jetty again to version 4.2.27?
> >>
> >> greets,
> >>   michi
> >>
> >>
> >> [1] http://kochtopf.twoday.net/topics/Brot+%26+Br%C3%B6tchen/
> >> [2] http://help.twoday.net/stories/3476002/
> >>
> >>
> >>
> >> --------------
> >>
> >> Jetty-4.2.27 - 22 November 2006
> >>  + Upgraded session ID generation to use SecureRandom
> >>  + AJP protected against bad requests from mod_jk
> >>
> >> Jetty-4.2.26 - 8 October 2006
> >>  + Backport of AJP fixes
> >>
> >> Jetty-4.2.25 - 4 Jan 2006
> >>  + Fixed aliasing of // for win32
> >>
> >> Jetty-4.2.24 - 7 April 2005
> >>
> >> Jetty-4.2.24rc1
> >>  + Fixed principal naming in FormAuthenticator
> >>
> >> Jetty-4.2.24rc0 - 8 March 2005
> >>  + Back ported Jetty 5 ThreadedServer and ThreadPool
> >>  + Added logCookie and logLatency support to NCSARequestLog
> >>
> >> Jetty-4.2.23.1 - 18 January 2006
> >>  + Fixed aliasing of // for win32
> >>
> >> Jetty-4.2.23 - 16 January 2005
> >>  + Cleaned up AbstractSessionManager synchronization.
> >>  + Fixed potential concurrent login problem with JAAS
> >>
> >> Jetty-4.2.23RC0 - 17 December 2004
> >>  + LineInput handles readers with small internal buffer
> >>  + Added LogStream to capture stderr and stdout to logging
> >>  + Support Secure and HttpOnly in session cookies
> >>  + Build unsealed jars
> >>
> >> Jetty-4.2.22 - 23 August
> >>  + fixed jaas logout for jetty-jboss integration
> >>  + fixed deployment of ejb-link elements in web.xml for jboss
> >>  + Added parameters for acceptQueueSize and lowResources level.
> >>
> >> _______________________________________________
> >> Helma-user mailing list
> >> Helma-user at helma.org
> >> http://helma.org/mailman/listinfo/helma-user
> >>
> > _______________________________________________
> > Helma-user mailing list
> > Helma-user at helma.org
> > http://helma.org/mailman/listinfo/helma-user
>
> _______________________________________________
> Helma-user mailing list
> Helma-user at helma.org
> http://helma.org/mailman/listinfo/helma-user
>