From: Gaius <james.a.rosen@gmail.com>
To: Rack Development <rack-devel@googlegroups.com>
Subject: Re: Trouble with Unicode in URLs
Date: Fri, 15 Jan 2010 09:16:09 -0800 (PST) [thread overview]
Message-ID: <88b1fe74-e0e0-482c-bcee-a41622c1cdb2@j4g2000yqe.googlegroups.com> (raw)
In-Reply-To: <2583a429-c946-4748-9bd5-aaf65673d0c3@a6g2000yqm.googlegroups.com>
I just found this older thread by you. If only we could just switch
computers!
http://groups.google.com/group/rack-devel/browse_thread/thread/d16abdccdb9026e8
On Jan 15, 12:13 pm, Gaius <james.a.ro...@gmail.com> wrote:
> Well, I don't have a problem. My point is that I had to build a
> middleware to solve the problem. To me, that indicates that some part
> of Rack (either core or contrib) might want this unencoding so others
> don't have the same problem. Of course, if it's really an httpd
> problem, I'd rather solve it there.
>
> I haven't done anything to httpd.conf other than add Passenger, as
> evidenced by the following diff:
>
> $ diff /etc/apache2/httpd.conf{,.original}
> 486d485
> < SSLSessionCache dbm:/var/log/apache2/ssl_gcache_data
> 490,507d488
> <
> < LoadModule passenger_module /Library/Ruby/Gems/1.8/gems/
> passenger-2.2.4/ext/apache2/mod_passenger.so
> < <IfModule passenger_module>
> < PassengerRoot /Library/Ruby/Gems/1.8/gems/passenger-2.2.4
> < PassengerRuby /System/Library/Frameworks/Ruby.framework/Versions/1.8/
> usr/bin/ruby
> < </IfModule>
> <
> <
> < # Added by the Passenger preference pane
> < # Make sure to include the Passenger configuration (the LoadModule,
> < # PassengerRoot, and PassengerRuby directives) before this section.
> < <IfModule passenger_module>
> < NameVirtualHost *:80
> < <VirtualHost *:80>
> < ServerName _default_
> < </VirtualHost>
> < Include /private/etc/apache2/passenger_pane_vhosts/*.conf
> < </IfModule>
> \ No newline at end of file
>
> On Jan 15, 12:03 pm, Iñaki Baz Castillo <i...@aliax.net> wrote:
>
> > El Viernes, 15 de Enero de 2010, Gaius escribió:
>
> > > 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.)
>
> > Then what is the problem now? :)
>
> > > 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)
>
> > Really interesting. Have you configured something in Apache2?
> > I have passenger 2.2.4 and apache2:
>
> > $ apache2ctl -v
> > Server version: Apache/2.2.11 (Ubuntu)
> > Server built: Nov 13 2009 22:06:57
>
> > In my case URL is unescaped by Apache2 ¿?
>
> > --
> > Iñaki Baz Castillo <i...@aliax.net>
>
>
next prev parent reply other threads:[~2010-01-15 17:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-01-15 16:26 Trouble with Unicode in URLs Gaius
2010-01-15 16:43 ` Iñaki Baz Castillo
2010-01-15 16:46 ` Gaius
2010-01-15 17:03 ` Iñaki Baz Castillo
2010-01-15 17:13 ` Gaius
2010-01-15 17:16 ` Gaius [this message]
2010-01-15 17:48 ` Iñaki Baz Castillo
2010-01-15 17:21 ` Gaius
2010-01-15 17:49 ` Iñaki Baz Castillo
2010-01-15 19:23 ` Gaius
2010-01-15 21:08 ` Iñaki Baz Castillo
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-list from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://groups.google.com/group/rack-devel
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=88b1fe74-e0e0-482c-bcee-a41622c1cdb2@j4g2000yqe.googlegroups.com \
--to=rack-devel@googlegroups.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).