Closed Bug 108877 Opened 23 years ago Closed 1 month ago

Select correct server for <news:msg-id> URLs

Categories

(MailNews Core :: Networking: NNTP, enhancement)

enhancement

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 1886132

People

(Reporter: BenB, Unassigned)

References

(Depends on 2 open bugs, Blocks 1 open bug)

Details

Support URLs of type <news:msg-id>, like <news:3BE8FDB2.2050705@logic.univie.ac.at>.

(E.g., try to enter them in the urlbar of the browser, should then also work for
Mailnews standalone msg windows.) We already support them for
<news://server:port/msg-id>, e.g.
<news://news.t-online.de/3BE8FDB2.2050705@logic.univie.ac.at>.
Depends on: 108876
Stephend, is this in the common RFCs or specs?
Yes.
Dup of "URI-parser fails for news:3B48D5FC.3030004@sc.rr.com"

*** This bug has been marked as a duplicate of 89939 ***
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
verified dup.
Status: RESOLVED → VERIFIED
No dup. The other bug is about the parser only (which I assumed does work
already). This bug is mainly to ensure that we select the right server (using
bug 108876). Maybe, if all deps are resolved, nothing is left here, but then we
should at least verify that it works. OTOH, there might need to be some glue
code to make it work together. REOPENing.
Status: VERIFIED → REOPENED
Depends on: 89939
Resolution: DUPLICATE → ---
Status: REOPENED → ASSIGNED
Target Milestone: --- → mozilla1.2
*** Bug 148659 has been marked as a duplicate of this bug. ***
Depends on: 37653
What's the status of this bug ?
It still does not work. My suggestion for a solution while we wait on the
dependencies is to use the servers in the order they are listed until we succeed.

Later, if we have the dependencies solved we should:
a) Retrieve from msg-store if available, else
b) Retrieve from default server if available, else
c) Retrieve from the other servers in the order they are listed as above.

I suggest to move the target milestone from the past to whatever and get it going;-)

pi
The support of very basic URLs is really needed. Requesting 1.3b blocking.

pi
Flags: blocking1.3b?
Flags: blocking1.3b? → blocking1.3b-
Depends on: 11076
Blocks: 11076
No longer depends on: 11076
No longer blocks: 11076
Depends on: 11076
Product: MailNews → Core
Updating summary per comment 5.
Summary: Support <news:msg-id> URLs → Select correct server for <news:msg-id> URLs
*** Bug 209011 has been marked as a duplicate of this bug. ***
Blocks: 311906
No longer blocks: 311906
Assignee: sspitzer → nobody
Status: ASSIGNED → NEW
QA Contact: stephend
Target Milestone: mozilla1.2alpha → ---
Switching out duped dep
No longer depends on: 108876
QA Contact: networking.news
Product: Core → MailNews Core
<http://www.apps.ietf.org/rfc/rfc1738.html> Section 3.6
<http://tools.ietf.org/html/draft-ellermann-news-nntp-uri-11#section-2.1>

Note: "news:" is *not* the same as "nntp:". It's completely different, and handling them the same is a bug.
Severity: normal → S3
See Also: → 1886132

This has been implemented in bug 1886132: For 'news' URIs without a specified server the first NNTP server found is used, which can be changed by reordering in Account Settings.

Status: NEW → RESOLVED
Closed: 23 years ago1 month ago
Duplicate of bug: 1886132
Resolution: --- → DUPLICATE
See Also: 1886132
You need to log in before you can comment on or make changes to this bug.