5 messages in ru.sysoev.nginxRe: integrate mod_rewrite into http_s...
FromSent OnAttachments
Aleksandar LazicApr 30, 2007 11:48 pm 
Evan MillerMay 1, 2007 9:29 am 
Aleksandar LazicMay 1, 2007 1:36 pm 
Igor SysoevMay 1, 2007 1:43 pm 
Ezra ZygmuntowiczMay 1, 2007 2:49 pm 
Actions with this message:
Paste this link in email or IM:
Paste this link in email or IM:
Atom feed for this thread
Paste this URL into your reader:
Subject:Re: integrate mod_rewrite into http_script_moduleActions...
From:Igor Sysoev (is-G@public.gmane.org)
Date:May 1, 2007 1:43:25 pm
List:ru.sysoev.nginx

On Tue, May 01, 2007 at 04:30:16PM +0000, Evan Miller wrote:

Aleksandar Lazic <al-nginx@...> writes:

I have yust read into the russian list that Igor plans to integrate the mod_rewrite functions into the http_script_module.

Sorry for my confusion, but can you explain a bit more what Igor plans? Will we be able to embed script directly into nginx.conf? Is mod_rewrite going away in favor of http_script_module?

Currently I want to replace ngx_http_rewrite_module with ngx_http_script_module only. I want to remove the "rewrite" directive, disable all static directives inside the "if" blocks, and leave only assignments, flow control, and some special directives as proxy_pass and fastcgi_pass inside "if" blocks.

And when would the script block? Would it be accessing disk or the network to get configuration? It might be nice especially for large sites to store configuration information in an external file or database, and then access it with an embedded script.

Non-blocking behaviour means that evaluating $forbidden variable for

if ($forbidden) { return 403; }

may include long query to remote site, and script VM should understand EAGAIN result when asks for variable, then it should return control to nginx, and then re-ask variable when it will be available and continue to execute the script code.