Ajax error in UI module installer when we are in the overlay

I only get this error if I press the back button in my browser, after installing a module with the built-in installer. Because then the installer tries to install the module once again, and throws this error.

Ah, sorry, then ignore my post. I copied it to the proper issue :)

Getting the same error message with 7.0 Release. Message flashes by very quickly every time I upload a new module - have to use a screen recorder to catch and play back slowly.

Get the following when installing a new module using Safari:

An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://www.MYHOST.ca/drupal/authorize.php?batch=1&render=overlay&id=9&op=do StatusText: ResponseText: ReadyState: 4

Slightly different message when installing a new module using Firefox:

An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://www.MYHOST.ca/drupal/authorize.php?batch=1&render=overlay&id=10&o... ResponseText: ReadyState: 4

Everything seems to work fine - error display just not a confidence builder. Advice appreciated.

I also get this error.

I also have noticed this error using 7.0 release. Again it doesn't fill me with confidence that everything is working correctly. I don't think I noticed it though before I installed the views module, this might be nothing though, as it may have simply been unnoticed rather than anything specifically related.

subscribing

Should be fixed by the current patch at #936686: "Installation failed" errors when installing modules from Update Manager w/ Overlay. Please help test that - thanks!

Downloaded & installed Drupal 7 today and had the same error.

An AJAX HTTP request terminated abnormally. Debugging information follows. Path: http://www.example.com/authorize.php?bath=1&render=overlay&id=4&op=do ResponseText: ReadyState 4

Subscribing.

Same error on different servers.

I also get this error.

Terrible. Drupal was supposed to be better and more stable than this. It is getting worse than its big cousin Joomla.

We should have a "thumbs down" feature for random unhelpful comments such as #13's.

For what it's worth, this error can be the result of misconfiguration. I encountered it when I accessed a site on a different domain than that specified by $base_url in settings.php. Although both domains worked fine in most cases, the base_url resulted in a cross-site scripting error in the browser. Updating the base_url to match the domain actually used for administration (and ajax calls) resolved the issue for me. Based on some of the comments (especially #10), this might be what some others are running into as well... Of course, this is a long-closed issue, so I won't worry too much about it...

$base_url has to be checked - had the same problem ...

Thanks witti (#15), saved me lots of time!! I had $base_url example.com, and a htaccess rewrite to www.example.com. Changing $base_url solved the problem.