squid configuration internal ipaddress

Hi,

I'm trying to setup squid with the following way:

--Ext. Net -- ¦FrontEnd Squid ¦ --- Cross over --- ¦ BackEnd¦

I want to isolate the back end webserver from the public network and
therefore I setu-up a front end server that runs squid and which his
connected to the back end via cross over cable in one of its
interface.

I have squid running as reverse proxy accelerator for the the back
end .

The problem is when the clients try send a POST request, they try to
connect directly to the back end server which has fake address (only
known to the front end).

Do you know what might be wrong with my setup, I would like that all
my HTTP requests would go via the front end squid server.

Thank you best regards
Hugo

Hello Hugo,

> The problem is when the clients try send a POST request, they try to
> connect directly to the back end server which has fake address (only
> known to the front end).

if the browser tries to send the POST data to the private IP obviously
the form's action or ajax setting is set to do so. Perhaps your
application hands out absolute URLs including a host-name resolving to
the private ip or the ip itself?

Regards
Manfred

Hi ,

Thank you for your answer, is there any way to confirm if the form is
using relative or absolute addresses?
>From what I can see (dump on the network the interface) after the POST
the back end server replies 302 with the absolute location off the
page,
including the internal address 192.168.0.77.

Dà è^@^Lè^@^M±ë^@P^Fo¼DD c#P^X^VÃk^@^@POST /
whtm_error_no_multiclient_support_form HTTP/1.0^M
Host: 192.168.0.77^M
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/
20050511 Firefox/1.0.4^M
Accept: text/xml,application/xml,application/xhtml+xml,text/
html;q=0.9,text/plain;q=0.8,image/png,*/*;q=0.5^M
Accept-Language: en-us,en;q=0.5^M
Accept-Encoding: gzip,deflate^M
Accept-Charset: ISO-8859-1,utf-8;q=0.7,*;q=0.7^M
Referer: http://front_end_squid/^M
Content-Type: application/x-www-form-urlencoded^M
Content-Length: 36^M
Via: 1.1 tpsrv100.cern.ch:80 (squid/2.5.STABLE3)^M
X-Forwarded-For: 133.133.133.133^M
Cache-Control: max-age=0^M
Connection: keep-alive^M
^M
¶<86>ñE%¥^E^@Z^@^@^@Z^@^@^@^@^BUþ3õ^@0HR^Bä^ H^@E^@^@L²^]@^@@^F^G
%è^@^Lè^@^M±ë^@P^Fo¾®D
c#P^X^VÃ[1m<8e>Ã^@^@htm_universalSubmit=Force
+Connecti^@^@^@Ã^@^@^@^@0HR^BÃ
¤^@^BUþ3õ^H^@E^T^@ÃfH^@^@<^F<96>lè^@^Mè^@^L^ @P±ëD
c#^Fo¾ÃP^X^P^@^CI^@^@HTTP/1.1 302 Found^M
Location: http://192.168.0.77/US/En_US-En_US-1193584791/whtm_load_index.htm^M
Content-Length: 0^M
Server: Allegro-Software-RomPager/3.12^M

Is there any way to change this behavior externally without changing
the application ?

Thank you best regards
Hugo

On 10 Mrz., 10:10, "manfred.doh...@gmail.com"
<manfred.doh...@gmail.com> wrote:
> Hello Hugo,
>
> > The problem is when the clients try send a POST request, they try to
> > connect directly to the back end server which has fake address (only
> > known to the front end).
>
> if the browser tries to send the POST data to the private IP obviously
> the form's action or ajax setting is set to do so. Perhaps your
> application hands out absolute URLs including a host-name resolving to
> the private ip or the ip itself?
>
> Regards
> Manfred