<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[URL rewriting]]></title><description><![CDATA[<p dir="auto">Hi,</p>
<p dir="auto">I'm totally an nb, and I'm trying out PFSense to see if it can support our environement.<br />
Installing was as easy as could be, but then the 'phun' started.<br />
Easy to connect to the internet, but I want to do a url rewriting/redirection from<br />
outside coming requests to different servers.</p>
<p dir="auto">I'm running a ESXi enverinoment with 6 servers which has to be served via PFsense for the right incoming url.</p>
<p dir="auto">So 123.mydomain.com has to be redirected to server 5<br />
1243.mydomain.com has to be redirected to server 3 etc…</p>
<p dir="auto">Wandering around for the whole day to figure it out  :-[</p>
<p dir="auto">Is there anyone out there who can point/help me out out how to get this done?</p>
<p dir="auto">Much regards,</p>
<p dir="auto">Ronald</p>
]]></description><link>https://forum.netgate.com/topic/14361/url-rewriting</link><generator>RSS for Node</generator><lastBuildDate>Mon, 12 Oct 2026 07:07:05 GMT</lastBuildDate><atom:link href="https://forum.netgate.com/topic/14361.rss" rel="self" type="application/rss+xml"/><pubDate>Fri, 27 Mar 2009 21:24:24 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to URL rewriting on Wed, 01 Apr 2009 08:29:25 GMT]]></title><description><![CDATA[<p dir="auto">Could also set up an extra VM with Apache configured as a relay.  Not the "cleanest" solution but it's not bad and the added latency is minimal.</p>
]]></description><link>https://forum.netgate.com/post/194260</link><guid isPermaLink="true">https://forum.netgate.com/post/194260</guid><dc:creator><![CDATA[Itwerx]]></dc:creator><pubDate>Wed, 01 Apr 2009 08:29:25 GMT</pubDate></item><item><title><![CDATA[Reply to URL rewriting on Sat, 28 Mar 2009 14:33:29 GMT]]></title><description><![CDATA[<p dir="auto">Not that I'm aware of.  The theory is that 2.0 will support relayd, which should be able to do what you want:</p>
<p dir="auto"><a href="http://b.blarg.org/2008/09/06/server-load-balancing-in-pfsense-13/" target="_blank" rel="noopener noreferrer nofollow ugc">http://b.blarg.org/2008/09/06/server-load-balancing-in-pfsense-13/</a></p>
]]></description><link>https://forum.netgate.com/post/193989</link><guid isPermaLink="true">https://forum.netgate.com/post/193989</guid><dc:creator><![CDATA[Cloverleaf]]></dc:creator><pubDate>Sat, 28 Mar 2009 14:33:29 GMT</pubDate></item><item><title><![CDATA[Reply to URL rewriting on Sat, 28 Mar 2009 08:22:57 GMT]]></title><description><![CDATA[<p dir="auto">So is there a kind off plugin wich can do the trick?</p>
]]></description><link>https://forum.netgate.com/post/193977</link><guid isPermaLink="true">https://forum.netgate.com/post/193977</guid><dc:creator><![CDATA[BigRonnyV]]></dc:creator><pubDate>Sat, 28 Mar 2009 08:22:57 GMT</pubDate></item><item><title><![CDATA[Reply to URL rewriting on Fri, 27 Mar 2009 22:21:53 GMT]]></title><description><![CDATA[<p dir="auto">PfSense is not really HTTP "aware", so you can't use it to do rewriting of URLs or redirecting based on request headers.  If the load balancer is revamped in 2.0, then you might be able to do so then, if they go with a layer 7 balancer.  If you have multiple IPs that you can use on the WAN, then you can create Port Redirections from these IPs (that you "give" to pfSense by adding them as Virtual IPs) to ports on the ESX servers, and then just map 123.mydomain.com to the proper frontend IP in DNS.</p>
]]></description><link>https://forum.netgate.com/post/193949</link><guid isPermaLink="true">https://forum.netgate.com/post/193949</guid><dc:creator><![CDATA[Cloverleaf]]></dc:creator><pubDate>Fri, 27 Mar 2009 22:21:53 GMT</pubDate></item></channel></rss>