Here's a way to kill two birds with one stone. SSL to HTTP bridging is a travesty and should never be used unless there are no authentication credentials required on the Web server and the Web server allows anonymous access.
So, deploy SSL to SSL bridging and that might fix it.
If not, come back with the exact details of the Web Publishing Rule.
I'm trying to implement this as well. It works on the root folder on the first connection however later on the connection fails. The problem is that for some reason it inserting the bridged port back in to the address. Details below:
I'm also having the same issue. ISA2004 and a Windows server 2003 webserver published with SSL to SSL. External SSL port is default 443, internal SSL port on the webserver is non-default. Bridging tab on pub rule says Webserver, redirect requests to SSL port. To tab: forward original host... enabled and requests appear from ISA Listener tab has SSL listener with wildcard cert.
Root folder is fine when opening as web folder, but when browsing I get redirected to the internal non-default SSL port. Also there is an extra folder made up by ISA I guess, the folder's name is the url with the internal port number like this example: webdav.domain.com:444
When browsing the site without web folders all is fine and the above folder is not there.
I've got it figured out: I unchecked the Forward original host header.... on the To tab and enabled Link Translation. I've entered the following dictionary entry: webdav.domain.com:444 and should be replaced with webdav.domain.com:443
In Content types enable Documents to be able to browse through subfolders. This also gets rid of the strange folder.