Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
web elements/images are not fully loaded
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
web elements/images are not fully loaded - 2.Jul.2008 11:47:11 AM
|
|
|
soimer
Posts: 8
Joined: 9.Apr.2007
Status: offline
|
Is there any mis-configuration in ISA publishing could cause web elements and images not fully loaded on the client side?
I've published a website (on a non-MS web server) using HTTPS. There are two versions of that website. The older version works perfectly, but when the new version comes, we use a new publishing rule, then some images just show half when page load is done, or some times the part of the sources code show in the web page (like a broken page); and also the speed is slower than before.
So just want to make sure the problem is not on the ISA publishing, and we can focus on other parts of this app. Thanks!
|
|
|
|
RE: web elements/images are not fully loaded - 7.Jul.2008 8:01:18 PM
|
|
|
soimer
Posts: 8
Joined: 9.Apr.2007
Status: offline
|
Thank you for looking into this.
Yes we are using SSL-SSL bridging.
One thing I need to add is between user and this ISA, there is a webseal server do another layer of authentication.
Also between ISA and webserver, the network is using kind of router-router load balancing.
Shall we also check if ISA has any conflict with those two factors?
Thanks!
|
|
|
|
|
RE: web elements/images are not fully loaded - 11.Jul.2008 11:36:01 AM
|
|
|
tshinder
Posts: 47439
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Definitely look into whether those devices are causing a problem. Try testing with just the ISA firewall in the path. If things work OK, then you can introduce the other devices into the mix and see which one of them is causing the problem.
HTH,
Tom
_____________________________
Thomas W Shinder, M.D.
Sr. Consultant/Technical Writer
Prowess Consulting http://www.prowessconsulting.com/
Blog: http://blogs.isaserver.org/shinder/
GET THE NEW ISA 2006 Book!: http://tinyurl.com/2gpoo8
|
|
|
|
|
RE: web elements/images are not fully loaded - 28.Jul.2008 2:51:54 PM
|
|
|
soimer
Posts: 8
Joined: 9.Apr.2007
Status: offline
|
Thanks for the reply. Here is something interesting I found on the Internet. Based on the fact that the website we're going to publish is hosted on Apache, I think they could be related. Any comments?
error 0x80090317 SEC_E_CONTEXT_EXPIRED
Had these errors occur for some users after 10-25 seconds of using bridged HTTPS connection to an apache webserver.
It turned out the maxkeepalive setting on apache was set to 100, and request 101 failed, causing the connection to fail and showing this error in ISA logs.
http://blogs.technet.com/isablog/archive/2006/04/03/423988.aspx
---------------------------
For a while I had been struggling with publishing a mediawiki site behind ISA. It would work fine for people using Internet Explorer but it would just show a blank page for people with Firefox or Safari. All browsers would display the content just fine if they went straight to the server and bypassed the ISA publishing rule. Checking the ISA logs I found that ISA was showing error 0x80090317 which means "The context has expired and can no longer be used". After spending some quality time with google and our local Linux/Apache guru it is now fixed by changing the KeepAlive setting to On in the Apache conf file of the mediawiki web server.
I'm not sure exactly why this fixes it, but it must mean that Firefox wants to create a second request on a connection when going through ISA but IE creates a second connection instead? And I guess that ISA must not allow Firefox to use that earlier connection? That's all I can put together as a theory.
http://forums.isaserver.org/m_2002039226/mpage_1/key_/tm.htm#2002039226
---------------------------
//
// MessageId: SEC_E_CONTEXT_EXPIRED
//
// MessageText:
//
// The context has expired and can no longer be used.
//
#define SEC_E_CONTEXT_EXPIRED _HRESULT_TYPEDEF_(0x80090317L)
http://msdn.microsoft.com/en-us/library/ms819775.aspx
SEC_E_CONTEXT_EXPIRED The application is referencing a context that has already been closed. A properly written application should not receive this error.
SEC_I_CONTEXT_EXPIRED The message sender has finished using the connection and has initiated a shutdown. For information about initiating or recognizing a shutdown, see Shutting Down an Schannel Connection.
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
