<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
<HTML><HEAD>
<META content=text/html;charset=gb2312 http-equiv=Content-Type>
<META name=GENERATOR content="MSHTML 8.00.7600.16535"></HEAD>
<BODY style="PADDING-LEFT: 10px; PADDING-RIGHT: 10px; PADDING-TOP: 15px"
id=MailContainerBody leftMargin=0 topMargin=0 CanvasTabStop="true"
name="Compose message area">
<DIV><FONT face=Calibri>Hi,</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>Company is testing nginx with a .net SOAP web service.
The nginx and web service runs on two different ports. The problem is the web
service returns the response with links that point to the web service's own TCP
port instead of the port of the Nginx.</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>Here is the config being used:</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>// ....</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV>server<BR>{<BR> listen
89;<BR> server_name mysolr;<BR></DIV>
<DIV> location /
{<BR> proxy_pass
<A
href="http://mysolr/">http://mysolr/</A>;<BR> proxy_redirect
off;<BR> proxy_set_header Host
$host:$server_port;<BR> proxy_set_header
X-Real-IP
$remote_addr;<BR> proxy_set_header
REMOTE-HOST
$remote_addr;<BR> proxy_set_header
X-Forwarded-For
$remote_addr;<BR> proxy_set_header
X-Forwarded-For $proxy_add_x_forwarded_for;<BR> }</DIV>
<DIV>}</DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>In the above case, response comes back with all embedded
links on port 80 rather than on 89. </FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>Any help is appreciated~</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV>
<DIV><FONT face=Calibri>Bing</FONT></DIV>
<DIV><FONT face=Calibri></FONT> </DIV></BODY></HTML>