screwed ACL on guildford proxy

[Frank]

I access webmail via https on port 2096.

Using the cache cache3-glfd.server.ntli.net I get the error:

Forbidden

You were denied access because:
Access denied by access control list.
Any ideas as to why? This webmail works fine using another cache.

[Paul]

Oops edit time;

I just noticed its https - remove the proxy server from https in your settings, you only need it for http.

[Frank]

I just noticed its https - remove the proxy server from https in your settings, you only need it for http.Well yeah I take your point.

BUT... The cache should not be intercepting requests on port 2096 anyway. This behaviour is displayed on all guildford caches too, but not other ntl caches.

Also, the fact that the cache should not be intercepting this https traffic is proven by other caches working without needing to implement the suggestion above (you are right by the way for normal ssl traffic, but cos it's on port 2096 this shouldn't be needed).

Which leads me to believe it is broken. I've also been using this cache for the last month or so and it has only broken today - nothing has changed on my PC grrr

[Frank]

Sorry, let me add Bristol to the list of screwed caches.

Tunnel or SSL Forbidden

Description: 2096 is not an allowed port for Tunnel or SSL connections

Some consistent failures please ntl? :)

[Paul]

Well yeah I take your point.

BUT... The cache should not be intercepting requests on port 2096 anyway. This behaviour is displayed on all guildford caches too, but not other ntl caches.

Also, the fact that the cache should not be intercepting this https traffic is proven by other caches working without needing to implement the suggestion above (you are right by the way for normal ssl traffic, but cos it's on port 2096 this shouldn't be needed).

Which leads me to believe it is broken. I've also been using this cache for the last month or so and it has only broken today - nothing has changed on my PC grrr
If you are manually setting your proxy and have it set for https as well as http then it is not a case of the cache intercepting it - you are forcing your https traffic to use the cache - and it is responding exactly as I would expect it to (on a port other than 443).

If it worked before then TBH I would say that was a fault or very poor security setting which they seem to have corrected.

Proxy servers will not normally respond to http or https requests on non standard ports - to prevent them being abused (like by spammers for instance).

[MetaWraith]

Sorry, let me add Bristol to the list of screwed caches.
[/b][/font]

Some consistent failures please ntl? :)

ssssssshhhhhhhh dont give them ideas.