Squid has a mechanism by which incoming URL's can be passed to an
external program to be rewritten and the reverse proxy subsequently
calls out to the rewritten URL
Is there a way to emulate this from within nginx
Changes with nginx 0.3.55 28 Jul 2006
*) Feature: the "stub" parameter in the "include" SSI command.
*) Feature: the "block" SSI command.
*) Feature: the unicode2nginx script was added to contrib.
*) Bugfix: if a "root" was specified by variable only, then the root
was relative to a server prefix.
*) Bugfix: if the request contained "//" or "/./" and escaped symbols
after them, then the proxied request was sent unescaped.
*) Bugfix: the $r->headers_in("Cookie") of the ngx_http_perl_module now
returns all "Cookie" header lines.
*) Bugfix: a segmentation fault occurred if
"client_body_in_file_only on" was used and nginx was switches to a
*) Bugfix: on some condition while reconfiguration character codes
inside the "charset_map" may be treated invalid; bug appeared in
i know you are in vacation and i'am also at end of the week but
something is burning in my head and therfore i want to ask ;-))
I'am not sure but the *proxy* modules (fcgi,http, ...) are they use a
form of connection pooling or make they always a
open(),send_datas(),read_data(),close() for there backend?
Have you ever heard about the scgi proto
Today i have looked into netcraft and was a little bit surprised:
07/2006 16 lighttpd 81224
06/2006 15 94895
07/2006 17 nginx 72630
06/2006 20 70111
Looks like that we need more english doc ;-))
Regards and have a nice vacation ;-)
Changes with nginx 0.3.54 11 Jul 2006
*) Feature: nginx now logs the subrequest information to the error log.
*) Feature: the "proxy_next_upstream", "fastcgi_next_upstream", and
"memcached_next_upstream" directives support the "off" parameter.
*) Feature: the "debug_connection" directive supports the CIDR address
*) Bugfix: if a response of proxied server or FastCGI server was
converted from UTF-8 or back, then it may be transferred incomplete.
*) Bugfix: the $upstream_response_time variable had the time of the
first request to a backend only.
*) Bugfix: nginx could not be built on amd64 platform; bug appeared in
Changes with nginx 0.3.53 07 Jul 2006
*) Change: the "add_header" directive adds the string to 204, 301, and
*) Feature: the "server" directive if the "upstream" context supports
the "weight" parameter.
*) Feature: the "server_name" directive supports the "*" wildcard.
*) Feature: nginx supports the request body size more than 2G.
*) Bugfix: if a client was successfully authorized using "satisfy_any
on", then anyway the "access forbidden by rule" message was written
in the log.
*) Bugfix: the "PUT" method may erroneously not create a file and
return the 409 code.
*) Bugfix: if the IMAP/POP3 backend returned an error, then nginx
continued proxying anyway.
Hi, I am curious if the above behaviour is okay as per the RFC. I
verified this behaviour by conifguring a backend lighttpd to send out
http/1.0 response via the following config
server.protocol-http11 = "disable"
nginx reverse proxying this however continues to respond with a
http/1.1 to the end client as evident
I am not sure if the RFC allows for this
I'm okay if this were configurable
Changes with nginx 0.3.52 03 Jul 2006
*) Change: the ngx_http_index_module behavior for the "POST /" requests
is reverted to the 0.3.40 version state: the module now does not
return the 405 error.
*) Bugfix: the worker process may got caught in an endless loop if the
limit rate was used; bug appeared in 0.3.37.
*) Bugfix: ngx_http_charset_module logged "unknown charset" alert, even
if the recoding was not needed; bug appeared in 0.3.50.
*) Bugfix: if a code response of the PUT request was 409, then a
temporary file was not removed.