Open Bug 2080906 Opened 1 month ago Updated 27 days ago

[exchange] Consider coupling incoming server properties with the base URL more strongly

Categories

(MailNews Core :: Networking: Exchange, task)

Product:
MailNews Core
Component:
Networking: Exchange
Type:
task

Tracking

(Not tracked)

People

(Reporter: babolivier, Unassigned)

References

(Blocks 1 open bug)

Details

We currently have two locations where e.g. an incoming server stores properties (username, hostname, port, socket type, etc): the URL (ews_url) and the server's properties.

Some parts of the code read those values from the properties accessors (e.g. GetPort, GetHost...) and some others read them from the URL after parsing it. If I remember correctly, this came out of concern that we would try reading from these properties before we have a URL set, but I'm not sure how much of a credible worry this is. There is room for these two sources to drift apart with the current configuration, and I think we should consider making all accessors read from the URL and error if it's not set.

You need to log in before you can comment on or make changes to this bug.