-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
> Sounds like you are trying to use the accel port as proxy port. You need
> one http_port for each function..
>
Yep, that was what I had in mind, because as written earlier I thought
it should be possible in theory.
But thanks for the clarification
ons 2010-02-24 klockan 16:27 +0100 skrev Bastian Spanneberg:
> Now, I added a parent proxy and proxy-authentication to the forwarding
> proxy configuration, and the new problem is, that when I use the
> instance as proxy now, I'm prompted for authentication for every host I
> visit/connect to.
So
tor 2010-02-25 klockan 16:40 +0100 skrev Bastian Spanneberg:
> should be possible to distinguish requests, as web server/accelerator
> requests should only be like
>
> GET /...
>
> and the proxy requests contain a complete URL.
Partially true. But then RFC2616 also says this:
To allow for t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thx again for the quick answer!
Amos Jeffries wrote:
> No.
> They need to be different port numbers. Sorry if that was not made clear
> enough.
> Regular proxy access on the standard proxy 3128 and web service on the
> standard web server port 80 with
Bastian Spanneberg wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amos Jeffries wrote:
Because the "accel" flag tells Squid to behave like th authoritative web
server for all incoming requests. When it needs auth it sends a web-server
auth challenge (linked to domain name by the browser t
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Amos Jeffries wrote:
> Because the "accel" flag tells Squid to behave like th authoritative web
> server for all incoming requests. When it needs auth it sends a web-server
> auth challenge (linked to domain name by the browser to prevent XSS
> credent
On Wed, 24 Feb 2010 16:27:44 +0100, Bastian Spanneberg
wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
> Thx again for the help, Henrik
>
>> localhost is not in your list of sites/domains to forward to the
>> SERVICES cache_peer...
>>
>> but most do not want this.. they want localhos
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thx again for the help, Henrik
> localhost is not in your list of sites/domains to forward to the
> SERVICES cache_peer...
>
> but most do not want this.. they want localhost services to be
> restricted to browsers running on the same box, not random
tis 2010-02-23 klockan 16:26 +0100 skrev Bastian Spanneberg:
> What still doesn't work is, that I can access the web apps running on
> the SERVICES machine via http://localhost. When I have the proxy enabled
> in my browser, I can visit access them via http://www.example.net, but
> localhost doesn
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Chris, Hi Henrik
> http://www.mail-archive.com/squid-users@squid-cache.org/msg61608.html
>
Thx for the hint.
I have at least a partly running configuration now, but still suffer
from different problems :)
Below is the upper part of my squid.con
Bastian Spanneberg wrote:
Hi all
I'm trying to find out if the following scenario is possible with Squid:
I want to run 1 instance of Squid, which acts as both, a proxy with
proxy authentication and as a reverse proxy for different web/app
servers in the back.
Is there a way for squid to disti
fre 2010-02-19 klockan 14:17 +0100 skrev Bastian Spanneberg:
> I want to run 1 instance of Squid, which acts as both, a proxy with
> proxy authentication and as a reverse proxy for different web/app
> servers in the back.
Ok.
Just keep in mind that you need never_direct rules for the reverse
pro
Hi all
I'm trying to find out if the following scenario is possible with Squid:
I want to run 1 instance of Squid, which acts as both, a proxy with
proxy authentication and as a reverse proxy for different web/app
servers in the back.
Is there a way for squid to distinguish between standard prox
13 matches
Mail list logo
