Hi Jörg, thanks for landing this. This fixes a long-standing issue. I'd even like this to be in TB 68.3, if that is accepted. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a 404. I think this is new. Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Bug 1185366 Comment 27 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a 404. I think this is new. Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a 404. I think this is new. (Welcome to my world of coding against Microsoft servers! :-( ) Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a 404. I think this is new. (Welcome to our world of coding against Microsoft servers! :-( ) Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read and adhere to specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a 404. I think this is new. (Welcome to our world of coding against Microsoft servers! :-( ) Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a 404. I think this is new. (Welcome to our world of coding against Microsoft servers! :-( ) Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a "not found". I think this is new. (Welcome to our world of coding against Microsoft servers! :-( ) Coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. If the first is available, we abort or ignore the second request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a "not found". I think this is new. (Welcome to our world of coding against Microsoft servers! :-( ) Not entirely coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.
Hi Jörg, thanks for landing this. This fixes a long-standing issue. Yes, indeed, it would be good for this fix to land in TB 68.3. > I'm a little confused that this code is run when setting up jk@yahoo.com. yahoo.com is directly available in the ISPDB. I see am0.yahoodns.net. For speed, we fire the 2 requests at the same time. [corrected:] If the second is available, we abort or ignore the first request. > the entire MS welcome page being dumped out in the log. I suggest addressing that in a separate bug > `client config xml = "\r\n\r\n\r\n<!DOCTYPE html>\r\n<html lang=\"de-de\" dir=\"ltr\">\r\n<head data-info` Yes, that must be because Microsoft, as usual, cannot read specifications, not even the most basic stuff like HTTP 404. They appear to send a HTTP 200 success and HTML page for a "not found". I think this is new. (Welcome to our world of coding against Microsoft servers! :-( ) Not entirely coincidentally, I ran into the same issue and fixed it while working on this bug, but didn't include it in the patch, because it's irrelevant here. I filed bug 1595991 with a patch to cut this down.