Welcome! Log In Create A New Profile


Re: Reverse proxy subdirectory

July 30, 2010 12:35AM
http://localhost:888/index.html (

<meta http-equiv="Pragma" content="no-cache">
<meta http-equiv="content-type" content="text/html; charset=utf-8">
<meta http-equiv="content-language" content="en">
var cur_controller = 0;
var cur_unit = -2;
var lastmessage = ""
var who = 1;
var lang = 0;
function init()
setTimeout("window.content.document.location.replace('/page0.html?c=0')", 500);
<title>3ware 3DM2 - superserver - Summary</title>
<noscript>(0x0C:0x0013): You must enable Javascript on your browser for 3DM 2 to run properly</noscript>
<frameset frameborder="no" rows="138,*" onLoad="init()">
<frame name="menu" scrolling="no" noresize src="/blank.html">
<frame name="content" src="/blank.html">

<p>(0x0C:0x0014): 3DM2 uses frames but your browser doesn't support them</p>

П.С. фреймы, кстати, тоже открываются, но картинки на них - нет, т.е. только первый запрос открывается корректно.

Вот здесь читал про апач http://www.apachetutor.org/admin/reverseproxies
там похожие настройки

ProxyPass /app1/ http://internal1.example.com/
ProxyPassReverse /app1/ http://internal1.example.com/
но рекомендуют
However, there is a slightly more complex alternative form that I recommend as more robust:
<Location /app1/>
ProxyPassReverse /

The reason for recommending this is that a problem arises with some application servers. Suppose for example we have a redirect:

HTTP/1.1 302 Found
Location: /some/path/to/file.html

This is a violation of the HTTP protocol and so should never happen: HTTP only permits full URLs in Location headers. However, it is also a source of much confusion, not least because the CGI spec has a similar Location header with different semantics where relative paths are allowed. There are a lot of broken servers out there! In this instance, the first form of ProxyPassReverse will return the incorrect response

HTTP/1.1 302 Found
Location: /some/path/to/file.html

which, even allowing for error-correcting browsers, is outside the Proxy's address space and won't work. The second form fixes this to

HTTP/1.1 302 Found
Location: /app1/some/path/to/file.html

which is still broken, but will at least work in error-correcting browsers. Most browsers will deal with this.

может что-то такое нужно?
Subject Author Posted

Reverse proxy subdirectory

andribas July 29, 2010 02:52PM

Re: Reverse proxy subdirectory

Igor Sysoev July 29, 2010 03:08PM

Re: Reverse proxy subdirectory

andribas July 30, 2010 12:35AM

Re: Reverse proxy subdirectory

andribas July 30, 2010 12:48AM

Re: Reverse proxy subdirectory

Igor Sysoev July 30, 2010 02:52AM

Sorry, only registered users may post in this forum.

Click here to login

Online Users

Guests: 84
Record Number of Users: 6 on February 13, 2018
Record Number of Guests: 421 on December 02, 2018
Powered by nginx      Powered by FreeBSD      PHP Powered      Powered by MariaDB      ipv6 ready