Rewriting/proxy_pass example

Server NGINX
1

my goal is the following

i want requests that come in this format…

http://d1.example.com
http://d2.example.com
.
.
http://dn.example.com

to proxy through to my web server as

http://hardcode.example.com/?site=d1
http://hardcode.example.com/?site=d2
.
.
http://hardcode.example.com/?site=dn

I would also like to pass the uri as is and just append the site=d1 to
the
request. for example

http://d1.example.com/processRequest?arg=1

to become
http://hardcode.example.com/processRequest?arg=1&site=d1

Can the proxy_pass/rewrite combination achieve this pattern?

I believe that hardcode.example.com doesn’t have to be the same domain
as
the src, its the moving of the subdomain to the argument parameter which
i
desire.

Thanks

2

On Wed, Dec 9, 2009 at 3:24 AM, Todd G. [email protected] wrote:

.
I believe that hardcode.example.com doesn’t have to be the same domain as
the src, its the moving of the subdomain to the argument parameter which i
desire.
Thanks

server
{
server_name ~(^d\d).example.com; # server block to use for
dN.example.com
set $name $1; # put the captured dN to $name variable
rewrite ^ http://hardcode.example.com$uri?$args&site=$name
permanent; # rewrite the url to correct address
}

–
O< ascii ribbon campaign - stop html mail - www.asciiribbon.org

3

On Tue, Dec 08, 2009 at 02:24:13PM -0600, Todd G. wrote:

to proxy through to my web server as
http://d1.example.com/processRequest?arg=1
desire.
0.8.29:

you should define the upstream to not resolve the host in runtime

upstream hardcode.example.com {
server hardcode.example.com;
}

server {
server_name ~^(?d\d+).example.com$;

location {
    proxy_pass  http://hardcode.example.com$request_uri?site=$site;
}

}

more early:

upstream hardcode.example.com {
server hardcode.example.com;
}

server {
server_name ~^(d\d+).example.com$;

location {
    proxy_pass  http://hardcode.example.com$request_uri?site=$1;
}

}

–
Igor S.
http://sysoev.ru/en/

4

On Wed, Dec 09, 2009 at 10:08:59AM +0300, Igor S. wrote:

http://dn.example.com
request. for example
I believe that hardcode.example.com doesn’t have to be the same domain as
server {
server_name ~^(?d\d+).example.com$;

location {
    proxy_pass  http://hardcode.example.com$request_uri?site=$site;

  •     proxy_pass

http://hardcode.example.com$request_uri?site=$site;

  •     proxy_pass  http://hardcode.example.com$uri?site=$site&$args;

server_name  ~^(d\d+)\.example\.com$;

location {
    proxy_pass  http://hardcode.example.com$request_uri?site=$1;

  •     proxy_pass  http://hardcode.example.com$request_uri?site=$1;

  •     proxy_pass  http://hardcode.example.com$uri?site=$1&$args;

}

}

–
Igor S.
http://sysoev.ru/en/