$httpBackend expectations with undefined URL

[Kapaacius]

Using : Angular-1.3.0-beta.17

$httpBackend.expect methods return true when URL is undefined or missing, even though the documentation states that the URL is not optional.

This is because of the following code in angular-mocks.js (class MockHttpExpectation):

this.matchUrl = function(u) {
    if (!url) return true;

A Plunkr to illustrate the point: http://plnkr.co/edit/k1bntn?p=preview

Is this an undocumented feature or a bug?

[positivew]

This bug/feature goes all the way back to version 1.0.0.

[petebacondarwin]

It seems to be an undocumented feature - i.e. if you don't specify a URL then it matches all URLs.
Is there a problem with this? If so can you provide a concrete demonstration of why it is a problem.
Otherwise I think a PR to update the docs would be reasonable.

[petebacondarwin]

@caitp suggested an explicit solution of "*" or null. I would be happy with that.

Can "*" be a valid URL itself? If so then we would not be able to check that the correct URL was requested if this acts as a wildcard. I would go for a solution such as an explicit null, since this cannot conflict with a valid URL.

In the meantime I would also be happy with updating most of those failing tests to use explicit URLs since most of them could be written that way.