This may not be an asp.net problem but one of our customers is running into
this with our asp.net application.
They log into our web application which is hosted on their servers. After
logging in, one different workstations each time, their IE 6.0 browser does
not let them click on certain HTML links. The links are regular HTML to the
browser, but when clicked nothing happens. No progress bar begins and the
browser doesn't respond. The application is running with frames. Links and
buttons on the other frames work great and still respond as does the start
menu and browser menus. If they right-click the link and go to open in a
new window, it opens a new window with the url but doesn't actually try to
access the url. They are forced to close the browser instance and re-login.
this happens on different machines and at different times and doesn't seem
to correlate to any particular pattern of usage. Our asp.net application
runs at over 14 other sites across the country and has been for over 3 yrs
without any issue like this. The customer did mention they were SSLing the
site, which our other customers do too, but they weren't sure if this would
cause such odd behavior.
The server side doesn't show any memory increase or anything funny happening
there and no timeouts are shown on the browser it simply doesn't begin the
asp.net request. Any ideas on this one?
Sincerely,
Christopher
this with our asp.net application.
They log into our web application which is hosted on their servers. After
logging in, one different workstations each time, their IE 6.0 browser does
not let them click on certain HTML links. The links are regular HTML to the
browser, but when clicked nothing happens. No progress bar begins and the
browser doesn't respond. The application is running with frames. Links and
buttons on the other frames work great and still respond as does the start
menu and browser menus. If they right-click the link and go to open in a
new window, it opens a new window with the url but doesn't actually try to
access the url. They are forced to close the browser instance and re-login.
this happens on different machines and at different times and doesn't seem
to correlate to any particular pattern of usage. Our asp.net application
runs at over 14 other sites across the country and has been for over 3 yrs
without any issue like this. The customer did mention they were SSLing the
site, which our other customers do too, but they weren't sure if this would
cause such odd behavior.
The server side doesn't show any memory increase or anything funny happening
there and no timeouts are shown on the browser it simply doesn't begin the
asp.net request. Any ideas on this one?
Sincerely,
Christopher