94962 - Can't post to servers with same hostname, but different ports

Status: RESOLVED DUPLICATE of bug 38137

(MailNews Core :: Networking: NNTP, defect)

Description

[Ben Bucksch (:BenB)]

Reproduction:
1. Set up a server/proxy host with n (n > 1) newsservers running at different
ports. The 2 newsservers should carry (at least partly) different groups.
2. Set up Mozilla news accounts for each of them
3. Try to read groups from each of them
4. Try to post to each of them, to groups which don't exist on the respecitive
other newsserver.

Actual result:
Step 3 works.
Step 4 fails (at least for n-1 servers)

Expected result:
All steps work for all newsservers

Additional Comments:
I use this setup to access different news servers through my proxy.

Comment 1

[Ben Bucksch (:BenB)]

Workaround: Add a fake hostnames to your /ets/hosts, pointing at the IP of the
server/proxy. Then, use these fake hostnames as hotnames in Mozilla's accounts.

The problem seems to be that some code thinks that an identical hostname means
an identical server, which is wrong.

Comment 2

[Håkan Waara]

cc networking guys.

Comment 3

[Ben Bucksch (:BenB)]

I guess that "some code" is in Mailnews.

Comment 4

[[e-mail] (gone - use [e-mail] instead)]

Looks like bug 55540 to me

*** This bug has been marked as a duplicate of 55540 ***

Comment 5

[Ben Bucksch (:BenB)]

The other bug is about the Account Manager, which works fine for me. REOPENing.

Comment 6

[Denis Antrushin]

Attachment: (hacky) patch

Comment 7

[Denis Antrushin]

Ben, could you try my patch (attachment 53095 [details] [diff] [review]) ?


This patch mades only *minimal* changes to code,
and not the best possible one, I think. May be I'll
come with better patch later :-)

Comment 8

[Ben Bucksch (:BenB)]

I don't have a current Mozilla build atm.

Comment 9

[Håkan Waara]

I'm not sure I about the hardcoded ':' part; if there are standard URI parsing 
facilities available, we should use those. Bbaetz or Darin would probably know 
about that.

Denis, perhaps if you looked at how other protocols handle this, we could do 
this consistently for news?

Thanks

Comment 10

[Bradley Baetz (:bbaetz)]

use nsnull instead of NULL.

There aren't parsing problems with this, since we're generating a host:port
string, not parsing one.

I'm not sure what the mailnews people think of the default paramaters, though.

Comment 11

[Denis Antrushin]

This port situation is quite unique for nntp service :-).
Also, other protocol handlers (imap, for example), uses
hardcoded chars/string when constructing character strings
for URIs.

As for default parameters, it's not a problem, I can make them
non-default. Also, I think it's a good idea to change parameter
order of FindServerWithNewsgroup and FindHostFromGroup:
(groupName, host, port) sequence looks more clear that
(host, groupName, port). What do you think?
I'll come with new patch in a moment...

Comment 12

[Denis Antrushin]

Attachment: No default parameters; changed parameters order

Comment 13

[Ben Bucksch (:BenB)]

Probably dup of bug 54911.

Comment 14

[[e-mail] (gone - use [e-mail] instead)]

*** Bug 170673 has been marked as a duplicate of this bug. ***

Comment 15

[(not reading, please use [e-mail] instead)]

sorry for the spam.  making bugzilla reflect reality as I'm not working on these bugs.  filter on FOOBARCHEESE to remove these in bulk.

Comment 16

[Serge Gautherie (:sgautherie)]

Filter on "Nobody_NScomTLD_20080620"

Comment 17

[Joshua Cranmer [:jcranmer]]

Not quite. It's the same problem as 38137, I believe.