291461 - "Live Bookmark feed failed to load" - RSS published by intranet unreachable without PROXY

Status: RESOLVED EXPIRED

(Firefox :: Bookmarks & History, defect)

Description

[Aristoteles]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

We have intranet portal solution in our company.
Intranet portal server is not reacheble through PROXY (ISA).
My connection setting in Firefox 1.0.3 is:
- Manual proxy configuration: Use the same proxy for all protocols __ ISA:8080
- No Proxy for: localhost, 127.0.0.1, infoportal.mycompany.com

I havn't any problems, when i go for RSS publish on internet:
http://news.bbc.co.uk/rss/newsonline_world_edition/front_page/rss091.xml

But if I go for RSS (through LiveBookmark functionality) published by our
intranet solution, Live Bookmark displaing me the message: "Live Bookmark feed
failed to load"



Reproducible: Always

Steps to Reproduce:
1. Place any RSS file to intranet web server (intranet.webserver.org/rss.xml)
2. Disable connection PROXY (packets direction) to any intranet web servers
3. Setup your Firefox - No Proxy for: intranet.webserver.org
4. Add Live Bookmark - http://intranet.webserver.org/rss.xml


Actual Results:  
Live Bookmark show the message:
"Live Bookmark feed failed to load" 

Expected Results:  
Load feeds got by Live Bookmarks.

Where is the problem from my point of view?
Even though value of "No Proxy for" on PROXY configuration is setup:
- intranet.webserver.org 

browser still try to reach RSS placed on intranet through PROXY.

Comment 1

[Kevin Brosnan]

This is likely related to bug 266348.

Comment 2

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 3

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.

Comment 4

[Mike Connor [:mconnor]]

sorry for bugspam, long-overdue mass reassign of ancient QA contact bugs, filter on "beltznerLovesGoats" to get rid of this mass change