On 17/10/2015 12:30 a.m., Gianluca Bergamo wrote:
> Ok thanks.
> Will that change the behavior of the proxy?
Of course. It will make it behave the way you apparently need it to.
Amos
___
squid-users mailing list
squid-users@lists.squid-cache.org
http:/
Ok thanks.
Will that change the behavior of the proxy?
On Fri, Oct 16, 2015 at 12:29 PM, Amos Jeffries
wrote:
> On 16/10/2015 11:16 p.m., Gianluca Bergamo wrote:
> > Hi Amos,
> >
> > Thank you for the support.
> > This is my squid.conf
> > http://pastebin.com/hNmnck27
> >
>
> I was right. You do
On 16/10/2015 11:16 p.m., Gianluca Bergamo wrote:
> Hi Amos,
>
> Thank you for the support.
> This is my squid.conf
> http://pastebin.com/hNmnck27
>
I was right. You dont have a reverse-proxy. You have a explicit/forward
proxy that happens to be listening on port 80.
To make it a reverse-proxy
Hi Amos,
Thank you for the support.
This is my squid.conf
http://pastebin.com/hNmnck27
We use squid as external access to hosts services (port 80) that are in a
vpn, so this should be the classical use of a reverse proxy.
What do you think?
Thank you.
Gian
On Fri, Oct 16, 2015 at 11:53 AM, Amo
On 16/10/2015 9:23 p.m., Gianluca Bergamo wrote:
> Hi everyone,
>
> I've just discovered that making requests to our reverse proxy using a
> Vodafone umts connection does not work.
> I get a bad request, and the problem is that in the http header the GET
> line does not include the full path but j
Hi everyone,
I've just discovered that making requests to our reverse proxy using a
Vodafone umts connection does not work.
I get a bad request, and the problem is that in the http header the GET
line does not include the full path but just the relative one. The "Host:"
parameter in the header is
