Bugzilla

Errors are inherent in the process, because we try multiple mechanisms and sources in getting a valid config, and most of these sources will not work, so they will error out. This is normal.

> autodiscover.xml
> XML Parsing Error: mismatched tag. Expected: </img>.

Here, GMX doesn't have an autoconfig file in the location, so they return a 404 with a HTML web page which shows the 404. )I don't know why we're not reacting to the 404, and ignore the result, but it doesn't make a difference in practice.) The HTML is not valid XML, even less so valid autoconfig XML, so we ignore that result. The process is designed to ignore all invalid results.

So, these errors are harmless. The error console is for developers. The error messages are useful for people trying to diagnose the autoconfig process for their own domain, to see why it fails and how they can fix it. So, supressing the errors would be detrimental. But given that the error console is only for experts and not for end users, this doesn't hurt anybody. I am just sorry for the spam, I agree in that I don't like error console spam. But these are just a few, and they are actually useful for debugging.

Hey Thomas,

errors are inherent in the autoconfig process, because we try multiple mechanisms and sources in getting a valid config, and most of these sources will not work, so they will error out. This is normal.

> autodiscover.xml
> XML Parsing Error: mismatched tag. Expected: </img>.

Here, GMX doesn't have an autoconfig file in the location, so they return a 404 with a HTML web page which shows the 404. )I don't know why we're not reacting to the 404, and ignore the result, but it doesn't make a difference in practice.) The HTML is not valid XML, even less so valid autoconfig XML, so we ignore that result. The process is designed to ignore all invalid results.

So, these errors are harmless. The error console is for developers. The error messages are useful for people trying to diagnose the autoconfig process for their own domain, to see why it fails and how they can fix it. So, supressing the errors would be detrimental. But given that the error console is only for experts and not for end users, this doesn't hurt anybody. I am just sorry for the spam, I agree in that I don't like error console spam. But these are just a few, and they are actually useful for debugging.

Hey Thomas,

errors are inherent in the autoconfig process, because we try multiple mechanisms and sources in getting a valid config, and most of these sources will not work, so they will error out. This is normal.

> autodiscover.xml
> XML Parsing Error: mismatched tag. Expected: </img>.

Here, GMX doesn't have an autoconfig file in the location, so they return a 404 with a HTML web page which shows the 404. (I don't know why we're not reacting to the 404, and consequently ignore the result, but it doesn't make a difference in practice.) The HTML is not valid XML, even less so valid autoconfig XML, so we ignore that result. The process is designed to ignore all invalid results.

So, these errors are harmless. The error console is for developers. The error messages are useful for people trying to diagnose the autoconfig process for their own domain, to see why it fails and how they can fix it. So, supressing the errors would be detrimental. But given that the error console is only for experts and not for end users, this doesn't hurt anybody. I am just sorry for the spam, I agree in that I don't like error console spam. But these are just a few, and they are actually useful for debugging.