Closed Bug 164785 Opened 24 years ago Closed 22 years ago

Unable to connect to news.com bookmark when bookmark is scheduled

Categories

(SeaMonkey :: Bookmarks & History, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: jfbustarret, Assigned: bugs)

References

()

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1) Gecko/20020826 When trying to connect to www.news.com, the status bar stays on "Transferring data from www.news.com" and nothing is displayed (it should redirect to news.com.com). Query : GET http://www.news.com/ HTTP/1.1 [headers] Answer : HTTP/1.0 301 Moved Permanently [headers] When trying to connect to news.com.com, nothing is displayed. DNS resolution is happening (CNAME www.com.com A xxx A xxx A xxx), but Mozilla does not connect to the web server (no TCP packet are seen by ethereal after the DNS resolution). Connection to www.com.com works. Reproducible: Always Steps to Reproduce: 1. connect to news.com.com 2. wait forever We use a squid proxy with a .pac configuration.
WFM - 1.1 release - WinXP By the way, I do not use any proxy.
wfm 20020826 on linux ISP problem?
No ISP problem : it works with IE. It's a major bug, because I am FORCED to use IE against my will...
Worksforme with Mozilla 1.1 release on Windows NT Mozilla/5.0 (Windows; U; WinNT4.0; en-US; rv:1.1) Gecko/20020826 Reporter, can you try again with HTTP-pipelining off, if that was enabled ?
Works for me on Solaris cvs 20020823. I'm behind a squid proxy.
Did some tests before lunch... Works the first time, and not the second/third/... time (with or without pipelining). Did some tests after lunch... Works every time. I'll do some more tests...
The fully qualified domain name doesn't look correct. There is double ".com". I have no knowledge that there is such a domain ".com" within another ".com".
com.com is a real domain, and is owned by CNET. I still have the problem. Apparently : - I can connect to news.com.com just after starting Mozilla, - After a variable amount of time (30s up to at last 10 minutes), I can't connect to news.com.com anymore.
Could Mozilla get confused by seeing the double ".com"?? Could Mozilla be lead to believe that it is that and not the domain name, "com.com"?
when connecting via a proxy server, mozilla only resolves the hostname of the proxy server. it does not resolve the hostname of the site you're trying to load... it leaves that up to the proxy server. reporter: it'd be helpful if you could attach a packet trace to this bug report. thx!
WFM, Moz 1.1 on Win95
wfm WinXP Pro, Moz1.1
wfm WinXP Pro, Moz1.1 - everytime, I tried five times
The keyword here is PAC, so if JF could post the PAC file as an attachment, that would be good to look at. Two things: Please try news.com.com directly. My experience is that you will get the same content. If that works, then we have a possible re-direct problem. (if you could post the complete headers of the 301, that would be great). If not, then we have a likely PAC problem w/ the domain. If you nslookup the IP address of news.com.com, and put it into the URL, you would probably find it works, which would isolate the problem.
Summary: Unable to connect to news.com → PAC: Unable to connect to news.com
I can't connect to news.com.com through its IP adress, because CNET uses virtual hosting and www.com.com is the default host. www.com.com or the IP address always work (even when news.com.com does not work). nslookup news.com.com : Name : www.com.com Addresses: 206.16.0.140, 206.16.0.141, 206.16.0.142, 206.16.0.143 206.16.0.145, 206.16.0.149, 206.16.0.134, 206.16.0.187 Aliases: news.com.com I tried this : 1. Switch to manual proxy config 2. Reboot PC 3. Launch Mozilla 4. Wait a few minutes (news.com.com always works just after launching Mozilla) 5. Type news.com.com => does not work 6. Type www.com.com => works (and works always) *** Ethereal does not see anything for the news.com.com request ! *** => Looks like it's not a .pac problem, and not a redirect problem... BTW, here are the HTTP headers of the redirect for http://www.news.com : HTTP/1.0 301 Moved Permanently Date: Tue, 27 Aug 2002 08:37:10 GMT Server: Apache Location: http://news.com.com Content-Length: 227 Content-Type: text/html; charset=iso-8859-1 X-Cache: MISS from internet2.tf1.fr X-Cache-Lookup: MISS from internet2.tf1.fr:8090 Proxy-Connection: keep-alive [HTML code]
set NSPR_LOG_MODULES=nsHttp:5 set NSPR_LOG_FILE=http.log mozilla 1. Surf www.news.com => OK 2. Surf slashdot => OK 3. Surf www.news.com => can't connect 4. Quit mozilla
Changing title. I have reproduced the problem. - news.com works when the bookmark is not scheduled (Check location for updates : 'Never') - news.com stops working when bookmark is scheduled (after the first schedule ?) Steps to reproduce : 1. Access www.news.com 2. Add bookmark 3. Display the bookmark's properties 4. Schedule : When (Every day), From (Midnight) to (11PM) Every (60) minutes 5. Notify : Change the bookmark's icon 6. Restart Mozilla 7. Wait 5 minutes 8. Click on the bookmark
Summary: PAC: Unable to connect to news.com → Unable to connect to news.com bookmark when bookmark is scheduled
I don't know why that is the case, but at least the cause is known. Before that you had me very confused.
I see the same problem with other web site www.theserverside.com. Same behavior. Schedule the bookmark. Try loading the bookmark manually. It hangs showing "Loading...". Turn off the scheduling. Restart Mozilla/Phoenix. Click on the bookmark. The link works. _shailesh
-> bookmarks
Assignee: darin → ben
Component: Networking: HTTP → Bookmarks
QA Contact: httpqa → claudius
Is this still a problem with current (1.7 beta or newer) builds ?
I can't reproduce this with Mozilla 1.7 branch build 2004041608 on windows XP. Does the bookmark actually have to change to show the update before the problem arises or is just setting it to schedule enough to break it?
Tested it with Firefox. It works...
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → WORKSFORME
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: