I''m getting a weird bug that only shows up on Internet Explorer (6) and not Firefox. When I click on a section that requires login, there''s a repeatable 30 second delay where IE seems to freeze. After 30 seconds, the login finally comes up. I''m using the latest lighttpd on the server. Problem didn''t occur when testing locally using Webrick.
on 9/1/2005 2:06 AM Bill Katz said the following:>I''m getting a weird bug that only shows up on Internet Explorer (6) >and not Firefox. When I click on a section that requires login, >there''s a repeatable 30 second delay where IE seems to freeze. After >30 seconds, the login finally comes up. I''m using the latest lighttpd >on the server. Problem didn''t occur when testing locally using >Webrick. >You don''t give much information, so there are many possibilities. If you answer these questions, you will probably find your answer. 1) Does the problem occur when Firefox identifies itself as IE using the User Agent Switcher extension? You''re not sniffing the browser are you? Is there javascript on your login page that is? Do you have javascript errors? Are you using a different style sheet for IE? 2) Is the domain name on the login page the same as the other pages? No, check DNS. Put the login domain DNS in your hosts file. 3) Does this happen on only 1 user''s IE or many users''? If only 1 user, clear these one at a time and retest: History, Cookies, Saved Passwords. If you want to be able to nail this problem down, you should save these so you can restore later. 4) Sniff the network traffic with Ethereal or TracePlus, monitor the app logs or just watch IE''s status bar very closely. You ought to be able to see whether the delay is entirely in the browser or if the browser is calling out to either your application or some other service. Do you have dynamic images on your login page? Is the freeze before or after the request for the login page? Before or after the server returns? The answers to these questions should point hard at a particular component. 5) Does it happen only for users in one domain? Some interaction with security zones? 6) Are you using https? Check you browser security settings, your certificates, and your authentication. 7) What about IE 5? IE on Mac? Safari? Opera? Now I''m reaching, but if you get here without solving your problem, it would be interesting to know
Bill, Can you post the relevant sections of your log file? Thanks, Derek On 9/1/05, Bill Katz <billkatz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I''m getting a weird bug that only shows up on Internet Explorer (6) > and not Firefox. When I click on a section that requires login, > there''s a repeatable 30 second delay where IE seems to freeze. After > 30 seconds, the login finally comes up. I''m using the latest lighttpd > on the server. Problem didn''t occur when testing locally using > Webrick. > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails >-- Derek Haynes HighGroove Studios - http://www.highgroove.com Keeping it Simple. 404.593.4879
This may be a lighttpd 1.4.2 / IE browser issue on 302 redirects. I swapped out lighttpd for webrick and the 30 second IE delay on 302 redirection disappeared. Still puzzled. Since 1.4.2 is a fairly new release (8/29), can anyone else see if this happens on their setup? I''m running Rails 0.13.1 on RHEL 3. Thanks. On 9/1/05, Bill Katz <billkatz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> I''m getting a weird bug that only shows up on Internet Explorer (6) > and not Firefox. When I click on a section that requires login, > there''s a repeatable 30 second delay where IE seems to freeze. After > 30 seconds, the login finally comes up. I''m using the latest lighttpd > on the server. Problem didn''t occur when testing locally using > Webrick. >
>> I''m getting a weird bug that only shows up on Internet Explorer (6) >> and not Firefox. When I click on a section that requires login, >> there''s a repeatable 30 second delay where IE seems to freeze. After >> 30 seconds, the login finally comes up. I''m using the latest lighttpd >> on the server. Problem didn''t occur when testing locally using >> Webrick.I''m experiencing exactly the same behavior, and it seems to be related to keep-alive. I also found that w/ Firefox it worked just fine. But IE seems to hang on all redirects. However, if I turn keep-alive off w/ the following line in my lighttpd.conf file: server.max-keep-alive-requests = 0 then it works just fine. I opened a ticket on the lighttpd site, as this seems to be a lighttpd issue, not a Rails one (since WEBrick works just fine). If anyone has other ideas....
Ray thanks for the extensive debugging tips. I''m going to keep it as a checklist for how to debug browser hiccups :) No javascript on that page. I try to put js links in only when needed. No separate stylesheet for IE. Not using https. As mentioned in a recent post, it''s probably a lighttpd issue and I''ll test out the fix later tonight.
I had exactly the same problem. I''ll see if the max-keep-alive-requests solves the problem. Thanks for the tip! Flurin Michael Schoen wrote:>>> I''m getting a weird bug that only shows up on Internet Explorer (6) >>> and not Firefox. When I click on a section that requires login, >>> there''s a repeatable 30 second delay where IE seems to freeze. After >>> 30 seconds, the login finally comes up. I''m using the latest lighttpd >>> on the server. Problem didn''t occur when testing locally using >>> Webrick. > > > I''m experiencing exactly the same behavior, and it seems to be related > to keep-alive. I also found that w/ Firefox it worked just fine. But IE > seems to hang on all redirects. > > However, if I turn keep-alive off w/ the following line in my > lighttpd.conf file: > > server.max-keep-alive-requests = 0 > > then it works just fine. > > I opened a ticket on the lighttpd site, as this seems to be a lighttpd > issue, not a Rails one (since WEBrick works just fine). > > If anyone has other ideas.... > _______________________________________________ > Rails mailing list > Rails-1W37MKcQCpIf0INCOvqR/iCwEArCW2h5@public.gmane.org > http://lists.rubyonrails.org/mailman/listinfo/rails
Thanks Michael. Adding> > server.max-keep-alive-requests = 0 >to the lighttpd.conf prevents the 30 second IE delay. Since I don''t have much of a load at the moment, it''s a good temporary fix.
I spoke too soon :( Tried to connect to lighttpd from IE at a different location over a satellite link and it doesn''t display on the redirect. For example, the login goes through and I''m actually logged in on the server, but the redirected screen never makes it back. Switched back to webrick and problem went away. On 9/3/05, Bill Katz <billkatz-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Thanks Michael. Adding > > > > server.max-keep-alive-requests = 0 > > > to the lighttpd.conf prevents the 30 second IE delay. Since I don''t > have much of a load at the moment, it''s a good temporary fix. >
Julian ''Julik'' Tarkhanov
2005-Sep-04 19:01 UTC
Re: 30 second delay in IE when redirecting to login?
On 1-sep-2005, at 15:35, Bill Katz wrote:> This may be a lighttpd 1.4.2 / IE browser issue on 302 redirects. > > I swapped out lighttpd for webrick and the 30 second IE delay on 302 > redirection disappeared. Still puzzled. Since 1.4.2 is a fairly new > release (8/29), can anyone else see if this happens on their setup? > I''m running Rails 0.13.1 on RHEL 3. Thanks.I observe a sensible delay with keep-alive on Safari with lighty running both on TxD and on my local powerbook. -- Julian "Julik" Tarkhanov