Closed Bug 116373 Opened 23 years ago Closed 21 years ago

Accessing secure sites via bookmark if they are down causes browser to hang.

Categories

(SeaMonkey :: Bookmarks & History, defect, P2)

x86
Linux
defect

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: poag, Assigned: bugs)

References

()

Details

(Keywords: hang)

From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:0.9.6+) Gecko/20011210 BuildID: 2001121008 A few days ago, I bookmarked this address. It so happens that the site is secure. Anyway, this box has been down and unresponsive for a few days. To see if it was back up and running, I chose this bookmark, and Mozilla hung with the Bookmarks menu stuck open. It'll stay there indefinately, disallowing any other input from the user. The bug is reproducible.. Just add the URL to your bookmarks file and have a swing at it. Reproducible: Always Steps to Reproduce: 1. Add https://209.53.17.13/~djw/XF86Config-4 to your Bookmarks. 2. Make sure that 209.53.17.13 (or the secure server of your choice) is unresponsive. :) 3. Attempt to bring up that page by selecting it from the Bookmarks menu. Actual Results: Bookmarks menu stays open and Mozilla hangs indefinately. Expected Results: Followed the normal behavior for reporting an inacessable site. AMD Duron 850, 384MB RAM, Red Hat 7.2 stock, nothing **** up or weird kernel-wise.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: hang
mass reassign of pchen bookmark bugs to ben
Assignee: pchen → ben
Priority: -- → P2
Target Milestone: --- → mozilla1.1
Works for me using Mozilla 1.3 on WinXP. Operation timed out. Bowie, are you still seeing this on a recent build of Mozilla?
Target Milestone: mozilla1.1alpha → ---
Marking WFM due to the last comment. Reopen if your opinion is different and you can reproduce this with a current build. Mozilla/5.0 (X11; U; Linux i586; en-US; rv:1.7a) Gecko/20040202
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.