Hi, all~
One of our editor girls have noticed recently a functionality regression while using the OpenResty admin site to do record search:
GET /=/model/Foo/url/http%3A%2F%
2Fwww.yahoo.cn%2Fhello%3Fabc%3D32
This request results in a 404 if the AllowEncodedSlashes directive is not explicitly turned on in your Apache2's config file, because encoded slash characters (i.e., %2F) in request URLs would give rise to bloody 404 responses in a default Apache setup. (This is not the case in lighttpd 1.4.x though.)
So please don't forget to add the following line to your httpd.conf:
AllowEncodedSlashes On
For more information, please see
http://httpd.apache.org/docs/2.2/mod/core.html#allowencodedslashes
as well as
http://github.com/agentzh/openresty/blob/master/lib/OpenResty/Spec/Install/Apache.podAlso, it's not recommended to run OpenResty with perl 5.10.0 due to its various memory leaks in its internals. We've observed very slow leaks while running OpenResty.pm with lighttpd 1.4.19 + perl 5.10.0. Lighttpd is also not recommended here because it does not automatically refresh its FastCGI worker processes periodically like Apache ;)
Cheers,
-agentzh