Re: HTTPS Using Web Proxy



Hi,

I've tried to get direct access to work but with no luck i'll keep
playing around and hopfully i'll get there in the end.

Kevin Longley wrote:

A simple way of testing if direct access will solve the issue is by
disabling the web proxy client on the local computer, within ie, and then
install the firewall client. If you can then access the website proceed with
configuring the site for direct access on the isa server. This is done on
the properties of the internal network object-web browser tab.

"Ken" <kend@xxxxxxxxxxxxxxxxx> wrote in message
news:6225ABB8-89FB-4B28-9C9C-E407B353D57E@xxxxxxxxxxxxxxxx
I am having the same problem. What do you mean when you say direct access?

Thanks Ken

"Kevin Longley" wrote:

I can't say. All I know that in my experience I have found several https
sites that had to be configured for direct access otherwise they would
exhibit the same symptoms that you described. I would experiment with a
couple of the sites using the direct access method.

<williams.ted@xxxxxxxxx> wrote in message
news:1164874666.025143.286050@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
It seems to be happening on every HTTPS Site and I noticed it's not
triggering any rules surely this is a problem with the configuration of
the ISA Server and not the website I'm trying to access?

Cheers

Kevin Longley wrote:

Some https sites will only work correctly if you configure them for
direct
access.

<williams.ted@xxxxxxxxx> wrote in message
news:1164815630.505278.84700@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Hi Everyone,
I've just setup my ISA server's web proxy and tested it by changing
my
web browser LAN settings to point to the ISA server. Everything is
working well on normal http traffic it records username and the
website
they are visiting but when it comes to https traffic I get an error
message in the web browser:

Network Access Message: The page cannot be displayed
Technical Information (for Support personnel)
Error Code: 504 Proxy Timeout. The connection timed out. (10060)
IP Address: xxx.xxx.xxx.xxx
Date: 29/11/2006 15:14:12 [GMT]
Server: isa.mydomain.com
Source: proxy

I've played around with some settings but I can't get it to work.
Settings I've tried include:
On the internal network properties / Web proxy page I enabled SSL on
port 8443,
I added HTTPS to the same rule as HTTP is working on; I've tried
enabling the web proxy filter in the application filters part of the
HTTPS Protocol,
In Internet Explorer I've unchecked Use Same Proxy Server for All
Protocols and changed the Secure setting to use port 8443
But still no luck.
When I look in the logs for normal HTTP that works I get first line
says:

8080 http Denied connection Anonymous
http://www.website.com HTTP/HTTPS Rule
80 http Allowed Connection MyUserName
http://www.website.com HTTP/HTTPS Rule
8080 http proxy Initiate Connection
No Rule

More or Less and that works fine
But when i try to connect to a website using HTTPS the log looks
like
this:

443 https initiate connection
No Rule
443 https Close connection
No Rule

Has Anyone got any suggestions I could try
Oh yeah I'm using ISA Standard 2006

Many thanks in advance






.



Relevant Pages

  • Re: HTTPS Using Web Proxy
    ... couple of the sites using the direct access method. ... Error Code: 504 Proxy Timeout. ... On the internal network properties / Web proxy page I enabled SSL on ... I added HTTPS to the same rule as HTTP is working on; ...
    (microsoft.public.isa)
  • Re: HTTPS Using Web Proxy
    ... A simple way of testing if direct access will solve the issue is by ... configuring the site for direct access on the isa server. ... I've just setup my ISA server's web proxy and tested it by changing ... I added HTTPS to the same rule as HTTP is working on; ...
    (microsoft.public.isa)
  • Re: HTTPS Using Web Proxy
    ... Direct Access did not help fix the problem. ... At first I was getting a error code: 502 Proxy Error and fixed that by ... I've just setup my ISA server's web proxy and tested it by changing ... I added HTTPS to the same rule as HTTP is working on; ...
    (microsoft.public.isa)
  • Re: MS Access cannot connect to external site via FTP
    ... and had to deal with the old MS Proxy2 which was a CERN Compliant Web Proxy ... the workstation is where it executes from, not the file server. ... Destination for "direct access" concerning the web proxy service. ...
    (microsoft.public.isa)
  • Re: HTTPS Using Web Proxy
    ... What do you mean when you say direct access? ... I've just setup my ISA server's web proxy and tested it by changing my ... Error Code: 504 Proxy Timeout. ... I added HTTPS to the same rule as HTTP is working on; ...
    (microsoft.public.isa)