Closed
Bug 853103
Opened 11 years ago
Closed 11 years ago
Autoconfig doesn't check <domain>/.well-known/
Categories
(Thunderbird :: Account Manager, defect)
Tracking
(Not tracked)
VERIFIED
INVALID
People
(Reporter: alex, Unassigned)
Details
User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:19.0) Gecko/20100101 Firefox/19.0 Build ID: 20130307023931 Steps to reproduce: Tries setting up autoconfig for my domain. I have a hosting Server with a script that returns the config.xml for a given email with the user name. (Build as descriped here: https://developer.mozilla.org/en-US/docs/Thunderbird/Autoconfiguration ) There is also a mention about what URLs are checked. First Thunderbird should check http://autoconfig.<domain>/mail/config-v1.1.xml and then http://<domain>/.well-known/autoconfig/mail/config-v1.1.xml Actual results: First one works perfekt. The second one not! I looked arround and see that if the domain has not entry for autoconfig Thunderbird does NOT make any try to check .well-known.. I did a capture with wireshark to see if the http request is mad and there is no connect at all. Expected results: Request to http://<domain>/.well-known/autoconfig/mail/config-v1.1.xml should have been made. But wireshark shows nothing as long as there is not entry for autoconfig on the domain.
Updated•11 years ago
|
Component: Installer → Account Manager
Updated•11 years ago
|
Summary: autoconfig not working correct → Autoconfig doesn't check <domain>/.well-known/
Comment 1•11 years ago
|
||
We do check it. http://mxr.mozilla.org/comm-central/source/mailnews/base/prefs/content/accountcreation/fetchConfig.js#62 However, we check the second only if the first didn't work. That is intentional. Does http://autoconfig.<domain>/mail/config-v1.1.xml work on your domain? Please tell us your concrete, actual domain, so that I can take a look.
Flags: needinfo?(alex)
Comment 2•11 years ago
|
||
I talked with the report per email. His DNS didn't have an entry for <domain>.
Status: UNCONFIRMED → RESOLVED
Closed: 11 years ago
Flags: needinfo?(alex)
Resolution: --- → INVALID
To be more specific there was no A record for the TOP Level like example.com A a.b.c.d only one for www.example.com. So to get the autoconfig to work without autoconfig entry make shoute the TOP Level of the domain points to the webserver you place the config-v1.1.xml on.
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•