Re: Trouble with Unicode in URLs

[Gaius <james.a.rosen@gmail.com>]

I agree with your analysis of _why_ the server is getting the hex-
escaped version. (That's why I used CGI.unescape to fix the problem.)
I'm also quite sure that Apache isn't unescaping before passing the
request on to Rack.

My setup:

$ apachectl -v
Server version: Apache/2.2.13 (Unix)
Server built:   Sep 28 2009 16:04:37

$ gem list passenger
*** LOCAL GEMS ***
passenger (2.2.4)


On Jan 15, 11:43 am, Iñaki Baz Castillo <i...@aliax.net> wrote:
> El Viernes, 15 de Enero de 2010, Gaius escribió:
>
> > I have a Rails app in which I'd like to use some Unicode URLs:
>
> >     # in routes.rb:
> >     map.resources 'proteges', :as => 'protégés', :only => [:index]
>
> > When I go tohttp://localhost:3000/protégés, I get
>
> >     No route matches "/prot%C3%A9g%C3%A9s" with {:method=>:get}
>
> > That was on Mongrel,
>
> Unicode symbols are not allowed in URL according to its BNF grammar. So the
> client (the web browser in your case) hex-escapes these symbols.
>
> This is: the client is sending a request like:
>
>   GET /prot%C3%A9g%C3%A9s HTTP/1.1
>
> which is correct.
>
> Then the server must hex-unescape it, and this is what you do with your Rack
> middleware :)
>
> Rack by itself doesn't require that the URL must be hex-unescaped before
> passing then to the application, so if a task for your application to do it.
>
> > though I also tried Passenger.
>
> And the same happened? I don't think so as Apache unescapes the URL before
> passing the request to the backend (in this case mod_rack). I've checked it
> before: when a request with hex-escaped URL arrives to Apache it unescapes
> before passing the data to mod_rack so you get the Rack variables hex-
> unescaped (you should already see the unicode symbols).
>
> I wonder how is possible your Apache not to unescape the URL before passing it
> to Rack, could you please re-check it? which Apache version do you use?
>
> --
> Iñaki Baz Castillo <i...@aliax.net>