There seems something wrong with the logic of this whole adjustment: The addons.json used to determine if there's a suitable add-on for the protocol (exchange) couldn't be loaded due to a delay in lookup. But we that is only (should only) be called *after* we found a config. And to find a config we ask the ISPDB, which is on *same* server we just queried to get a configuration in the first place! All setup should already be done when we go into the next call. Am I missing something? (I think increasing the timeout is alright though.)
Bug 1572418 Comment 34 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There seems something wrong with the logic of this whole adjustment: The addons.json used to determine if there's a suitable add-on for the protocol (exchange) couldn't be loaded due to a delay in lookup. But that is only (should only) be called *after* we found a config. And to find a config we ask the ISPDB, which is on *same* server we just queried to get a configuration in the first place! All setup should already be done when we go into the next call. Am I missing something? (I think increasing the timeout is alright though.)
There seems something wrong with the logic of this whole adjustment: The addons.json used to determine if there's a suitable add-on for the protocol (exchange) couldn't be loaded due to a delay in lookup. But that is only (should only) be called *after* we found a config. And to find a config we ask the ISPDB, which is on *same* server we just queried to get a configuration in the first place! All network setup should already be done when we go into the next call. Am I missing something? (I think increasing the timeout is alright though.)