Note - all of this is due to bugs Microsoft have recognised in Internet Explorer 5.5 Service Pack 1 and above (including IE6. Thanks for the help - it was the exact right answer. We now intend to update the CSS, but can do it in a less immediate way. We decided changing the Apache configuration was less risky than upgrading CSS software version and the problem has been solved. We could either tackle this by upgrading our CSS using the above patch information, or configuring our Oracle 9iAS / Apache to stop keep-alives when serving pages to Internet Explorer requests. The browser then tries to re-use this connection when you navigate on a page, causing an immediate "This page cannot be displayed - Cannot find server or DNS error" error message. We got hold of the Cisco bug reports and they agreed with our Apache/Internet Explorer 5.5SP1 and above reports - it's due to an IE bug with SS元.0 causing closed connections to be re-used by the browser.Įffectively, the client opens multiple TCP connections to the website, they then go into state CLOSE_WAIT rather than TIME_WAIT. There is very little config about the CSS SSL module but it's a very new product (I believe) hence my clutch at straws questions here! We are using a pair of CSS11506 in redundat straight-through config, i.e inline between firewalls and switches where the web servers hang-off. It looks like bypassing proxy servers fixes the issue, but as this is an open-to-all-comers website it should behave like any other one and hence shouldn't need the end users to do anything special! ![]() I'm not convinced the CSS is the root cause of the error, but having delegated SSL from Apache to the CSS it's much harder to spot what might be going on! Users can't easily move from IE as some are behind ISA proxies, but those behind Squid don't work at all, so Squid has some issues with our site. May be worth poiting out site is completely dynamic with no static pages running Apache 1.3.2 ![]() A view of the source shows the links to be well formed. TCP/IP is a protocol used by devices to communicate over the Internet and local networks. When the problem occurs, a hit of the browser Refresh brings up the correct page. Mainly seems to happen on POST operations, but again is inconsistent. on the browser on the guest machine returns: 'Cannot find server or DNS Error' This despite the new server certificates provided, the proper configuration of the web site the verification that port 443 is being listened to. Some times it works, some times it does not. Re: Unable to connect to web sites On Vbox VM using SSL. Hi Giles, problem appears to be IE related and we are currently investigating Apache directives for IE around keep-alives.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |