Ummm, what thread did I hijack? This was a fresh post. If there was another conversation going on with exactly what my issues was, I apologize. In any case, my issue is resolved. - Nick -----Original Message----- From: François Cami [mailto:fcami@xxxxxxxxxx] Sent: Friday, February 22, 2008 12:25 PM To: Nick Duda Cc: squid-users@xxxxxxxxxxxxxxx Subject: Re: Reverse Proxy, getting 503 errors when POST Hi Nick, Please do not hijack threads [1] on a mailing list, it makes things harder to follow and is not good practice. Best, François [1] http://en.wikipedia.org/wiki/Thread_hijacking On Tue, 19 Feb 2008 12:54:56 -0500 "Nick Duda" <nduda@xxxxxxxxxxxxxx> wrote: > Return-Path: <squid-users-return-80064-fcami=winsoft.fr@xxxxxxxxxxxxxxx> > Received: from [172.16.4.134] (HELO proxy.winsoft.fr) > by winsoft.fr (CommuniGate Pro SMTP 4.1.8) > with SMTP id 9170201 for fcami@xxxxxxxxxx; Tue, 19 Feb 2008 20:20:18 +0100 > Received: from (squid-cache.org [12.160.37.9]) by proxy.winsoft.fr with smtp > id 616a_ac8b072a_df1f_11dc_8c28_0013723ca92b; > Tue, 19 Feb 2008 20:20:05 +0100 > Received: (qmail 98351 invoked by uid 1007); 19 Feb 2008 17:55:45 -0000 > Mailing-List: contact squid-users-help@xxxxxxxxxxxxxxx; run by ezmlm > Precedence: bulk > List-Id: Squid Users <squid-users.squid-cache.org> > List-Post: <mailto:squid-users@xxxxxxxxxxxxxxx> > List-Help: <mailto:squid-users-help@xxxxxxxxxxxxxxx> > List-Unsubscribe: <mailto:squid-users-unsubscribe@xxxxxxxxxxxxxxx> > List-Subscribe: <mailto:squid-users-subscribe@xxxxxxxxxxxxxxx> > Delivered-To: mailing list squid-users@xxxxxxxxxxxxxxx > Received: (qmail 98339 invoked by uid 26); 19 Feb 2008 17:55:44 -0000 > X-MimeOLE: Produced By Microsoft Exchange V6.5 > Content-class: urn:content-classes:message > MIME-Version: 1.0 > Content-Type: text/plain; > charset="us-ascii" > Content-Transfer-Encoding: quoted-printable > Date: Tue, 19 Feb 2008 12:54:56 -0500 > Message-ID: <D9708869AB43DC4EA1BBED0D9A0E3658CF2F8B@xxxxxxxxxxxxxxxxxxxxxxxx> > In-Reply-To: <20080219143001.B89BC3BF@xxxxxxxxxxxxxxxxxxxx> > X-MS-Has-Attach: > X-MS-TNEF-Correlator: > Thread-Topic: Reverse Proxy, getting 503 errors when POST > Thread-Index: AchzDIhty/Ay28GtQPmvoDPFh0YVbwAEsRmA > References: <20080218121149.GG31322@xxxxxxxxxxxxxxxxxxxxxxxxx><fa6a0cb50802180541v2d629810g11ade574a413ccd2@xxxxxxxxxxxxxx><20080218135804.GL31322@xxxxxxxxxxxxxxxxxxxxxxxxx><fa6a0cb50802190540j55c11042u8280703dc4584557@xxxxxxxxxxxxxx> <20080219143001.B89BC3BF@xxxxxxxxxxxxxxxxxxxx> > From: "Nick Duda" <nduda@xxxxxxxxxxxxxx> > To: <squid-users@xxxxxxxxxxxxxxx> > X-OriginalArrivalTime: 19 Feb 2008 17:54:58.0874 (UTC) FILETIME=[8B07A1A0:01C87320] > X-Greylist: Recipient e-mail whitelisted, not delayed by milter-greylist-3.0 (squid-cache.org [12.160.37.9]); Tue, 19 Feb 2008 10:55:44 -0700 (MST) > X-Virus-Scanned: ClamAV 0.91.2/5886/Tue Feb 19 01:09:14 2008 on squid-cache.org > X-Virus-Status: Clean > Subject: Reverse Proxy, getting 503 errors when POST > > I've setup a very basic reverse proxy (maybe the error is because of my > config). It appears to be working as the reverse proxy properly, however > I can not perform a HTTP POST , I get TCP_MISS/503 error in my > access.log > > Basically, any request to the Public IP of my proxy on 80/443 (secured > by ACL's for certain IP's) I want to proxy the request to an internal > (behind firewall) webserver. > > Client sets host file like: > x.x.x.x www.some.domain.com > > Client surfs to www.some.domain.com, the ip is the public ip of squid > and they get served up the internal (behind firewall) site, this works, > but when they attempt to perform anything "POST" it doesn't allow: > > squid.conf (this is how its build for a test, I will clean it up and > lock it down more after) > > http_port 80 transparent > cache_peer x.x.x.x parent 80 0 no-query originserver > cache deny all > http_access allow all > > x.x.x.x = RFC1918 of internal web server > I had to use transparent because when I used accel with defaultdomain=, > cookies would only work for that domain. I have 5 different host entries > that need to be used to all hit the same internal ip/web server. > > What else is required or what is the issue on why I cant POST? I'm new > to this reverse configuration, so be kind lol > > Nick
