Difference between revisions of "Apache/Proxy"
Jump to navigation
Jump to search
(Created page with "{{DISPLAYTITLE: Apache mod_proxy recipies}} == Recipies == === IPv6 enable a IPv4 only site with reverse proxying === ==== Prerequisites ==== * mod_proxy is loaded * mod_h...") |
|||
(5 intermediate revisions by the same user not shown) | |||
Line 3: | Line 3: | ||
== Recipies == |
== Recipies == |
||
=== IPv6 enable |
=== IPv6 enable an IPv4 only site with reverse proxying === |
||
==== Prerequisites ==== |
==== Prerequisites ==== |
||
* mod_proxy is loaded |
* mod_proxy is loaded |
||
* mod_http_proxy is loaded |
* mod_http_proxy is loaded |
||
* An AAAA record in DNS with the same name as the website |
* An <tt>AAAA</tt> record in DNS with the same name as the website |
||
* An A record in DNS like ipv4.<domain> pointing the same IP as the website. |
* An <tt>A</tt> record in DNS like ipv4.<domain> pointing the same IP as the website. |
||
* Optional: mod_headers if downstream headers need to be modified. |
|||
<VirtualHost [ |
<VirtualHost [2001:db8:d0:d0]:80> |
||
ServerName bun.ch |
ServerName bun.ch |
||
ServerAlias www.bun.ch |
ServerAlias www.bun.ch |
||
Line 29: | Line 30: | ||
</IfModule> |
</IfModule> |
||
</VirtualHost> |
</VirtualHost> |
||
Interesting bit here is what Apache sends to the server downstream. Below is a request header observed via <tt>tcpudump</tt>. Depending on the far end one may need to modify the headers with <tt>mod_headers</tt> especially the <tt>Host:</tt> to make this work. |
|||
GET /test/ HTTP/1.1 |
|||
<span class="highlight">Host: ipv4.bun.ch</span> |
|||
User-Agent: Mozilla/5.0 [...] |
|||
Accept: text/html,application/xhtml+xml; |
|||
Accept-Language: en-US,en; |
|||
Accept-Encoding: gzip, deflate |
|||
Referer: http://bun.ch/ |
|||
<span class="highlight">X-Forwarded-For: 2001:db8::9090</span> |
|||
<span class="highlight">X-Forwarded-Host: bun.ch</span> |
|||
<span class="highlight">X-Forwarded-Server: bun.ch</span> |
|||
Connection: Keep-Alive |
|||
[[Category: Apache]] [[Category:IPv6]] |
Latest revision as of 10:59, 12 November 2016
Recipies
IPv6 enable an IPv4 only site with reverse proxying
Prerequisites
- mod_proxy is loaded
- mod_http_proxy is loaded
- An AAAA record in DNS with the same name as the website
- An A record in DNS like ipv4.<domain> pointing the same IP as the website.
- Optional: mod_headers if downstream headers need to be modified.
<VirtualHost [2001:db8:d0:d0]:80> ServerName bun.ch ServerAlias www.bun.ch LogLevel warn ErrorLog /var/log/apache2/bun.ch-ipv6-proxy.error.log CustomLog /var/log/apache2/bun.ch-ipv6-proxy.access.log combined <IfModule mod_proxy.c> ProxyRequests On <Proxy http://ipv4.bun.ch/*> Order deny,allow Allow from all ProxySet connectiontimeout=5 timeout=30 </Proxy> <LocationMatch "/"> ProxyPass http://ipv4.bun.ch/ ProxyPassReverse http://ipv4.bun.ch/ </LocationMatch> </IfModule> </VirtualHost>
Interesting bit here is what Apache sends to the server downstream. Below is a request header observed via tcpudump. Depending on the far end one may need to modify the headers with mod_headers especially the Host: to make this work.
GET /test/ HTTP/1.1 Host: ipv4.bun.ch User-Agent: Mozilla/5.0 [...] Accept: text/html,application/xhtml+xml; Accept-Language: en-US,en; Accept-Encoding: gzip, deflate Referer: http://bun.ch/ X-Forwarded-For: 2001:db8::9090 X-Forwarded-Host: bun.ch X-Forwarded-Server: bun.ch Connection: Keep-Alive