Great. That's progress.
I do not use an Apache frontend in front of my personal Roller instance,
so I don't have anything to share. Maybe other users can help here.
Here are some things you should check carefully:
First, if you are using auto conf between Apache and Tomcat, make sure
that the Apache side of the mod_jk / AJP configuration is updated after
you configured your Tomcat properly. This may require restarting the
Apache server.
If you have Roller set up properly. The permalink should get URL
encoded by Roller (with % hex values of the non-ASCII UTF-8 characters).
The URL should go out to the browser and come back in this same form.
Everything will work fine if this happens. That is the behavior you
should be seeing now when you go directly to the Tomcat HTTP port.
My guess is that the character encoding is getting mangled by rewriting
rules you have set up with mod_rewrite in Apache. If your rewriting
rules are not written properly, the entire URL may be decoded and
transmitted improperly either on the outbound path or on the inbound
path. I think it is possible to pass portions of the URL verbatim
through the rewrite rules, and that if you do this, I think you will be
ok. But I am not an expert in Apache rewrite rules.
I hope this helps.
--a.
Guglielmo Carandente wrote:
Thanks, so it's work... the problem is apache...could you send me your
apache configuration, so I compare it with my configuration...
Thanks a lot :-)
-----Messaggio originale-----
Da: Anil Gangolli [mailto:[EMAIL PROTECTED]
Inviato: giovedì 9 ottobre 2008 19.15
A: [email protected]
Oggetto: Re: Problem with special chars like èìòù in entry permalink
To help distinguish between an issue on the Roller side or the Apache
frontend, here is what I would suggest.
From inside your firewall, use your browser to navigate to the URL.
Then edit the address bar replacing the hostname in the URL with the
internal hostname or ip address of the Tomcat host and the HTTP
Connector port 11080 that you have configured. See if you can then
load the entry properly. If so, it indicates that the problem is on the
Apache webserver side, and you will need to check what encoding is being
applied there.
--a.
Anil Gangolli wrote:
It looks from headers that you are using an Apache webserver
frontend: Apache/2.2.3 (Debian) mod_jk/1.2.18
Make sure that the URIEncoding="UTF-8" attribute is set on the AJP
Connector as well.
If you are doing re-writing or any parsing of the URL on the Apache
webserver end, it might need to be configured to use UTF-8.
--a.
Guglielmo Carandente wrote:
I make all changes, but alwais don't work...
But is strange
Link
http://blog.kisskiss.it/kblog/telegu/entry/è_bello don't work
http://blog.kisskiss.it/kblog/telegu/entry/e_bello work
but in database anchor is è_bello
....
-----Messaggio originale-----
Da: Anil Gangolli [mailto:an
