URL_MATCHER should match url with missing f-slash at the end about angular.js HOT 5 CLOSED

Have already created branch to fix it:
http://github.com/vojtajina/angular.js/tree/fix-url-matcher

from angular.js.

let me know when it is ready for review and integration.

from angular.js.

is this: http://www.angularjs.org#xx a valid URI? we should check the RFC before we support it.

+1 on testing the regexp separately

from angular.js.

Thanks for note about RFC, I didn't think about it...
You can check RFC, they say:

An HTTP URL takes the form:
http:// <host> : <port> / <path> ? <searchpart>
where <host> and <port> are as described in Section 3.1. If :<port>
is omitted, the port defaults to 80.  No user name or password is
allowed.  <path> is an HTTP selector, and <searchpart> is a query
string. The <path> is optional, as is the <searchpart> and its
preceding "?". If neither <path> nor <searchpart> is present, the "/"
may also be omitted.

So, that means http://www.server.com is a valid url, but you are right, it's always good to add the forward slash.
Important thing is, that URL_MATCH is parser, not validator !

According to the rfc specification, "/" is not part of the path ! But check the javascript object window.location, at least in Firefox: "/" is part of the path property...

It's easy to change the regexp, that "/" would not be part of the url, but I would prefer to keep current behavior...

Well, I hope this patch is ready, the issue is fixed, whole branch is rebased to one commit.
Anyway, it would be good to add some more tests, consider adding more protocols (currently just http, https, ftp, file), etc...

from angular.js.

fixed via #68

from angular.js.