Force refreshing on a route causes $location.path() to be wrong.

[Siyfion]

When I navigate to a route such as http://www.test.com/products/management and force a refresh, the $routeProvider fails to match it against any routes and pushes me back to http://www.test.com/products (not even a valid route!). I think that this is because $location.path() incorrectly reports the current path as /management.

Here's my route configuration for reference:

  angular.module('labelLogicLiveApp')
    .config(function ($locationProvider, $routeProvider) {

      // Use HTML5 strategy if available.
      $locationProvider.html5Mode(true).hashPrefix('!');

      $routeProvider
        .when('/', {
          templateUrl: '/views/home.html'
        })
        .when('/user/login', {
          templateUrl: '/views/user_login.html'
        })
        .when('/product/management', {
          templateUrl: '/views/product_management.html',
          resolve: { isAuth: 'authService' }
        })
        .when('/product/:productId', {
          templateUrl: '/views/product_details.html',
          resolve: { isAuth: 'authService' }
        })
        .otherwise({
          redirectTo: '/'
        });
    });

[thatmarvin]

I see this too. Looks like a regression introduced in 1.1.5, as it was working fine in 1.1.4. The only precondition to trigger this is to load the url without #/, no force refresh needed.

[kapusta]

Seeing the same thing and can corroborate the part where it was working in 1.1.4

I have a few routes in my app with varying lengths and the behavior I'm seeing is that the last slash and stuff behind it is gone. So a route like /display/foo/123 becomes /display/foo and something like /create/foo becomes /create

[Siyfion]

Ah, and there was me thinking it could just be me being silly! lol. I'm going to test in 1.1.4 to double check that this has been introduced in 1.1.5 and report back.

[Siyfion]

I can confirm that this bug was definitely introduced in v1.1.5; v1.1.4 works fine.

[geddski]

Duplicate of #2774
I ran a git bisect and found it was commit 58ef323

[ilplotkin]

$location.path() on http://server/path/file.html returns file.html in 1.1.5 (it returned empty string in 1.1.4).
Looks like that it's related issue.

[petebacondarwin]

Actually #2774 is a duplicate of this one!

[Siyfion]

I was just about to say... You can't close them both! 😄

[petebacondarwin]

I think the issue is here https://github.com/angular/angular.js/blob/master/src/ng/location.js#L504

[clkao]

You can workaround the issue in 1.1.5 by adding <base href="/">, as mentioned in #2799 (comment)

[geddski]

Adding a element is not a good solution. It changes the way the browser handles relative paths and breaks many third-party libraries/widgets, especially those that use urls in SVG like some color pickers.

[IgorMinar]

Are you guys setting base[href] in your apps?

What @clkao mentioned is not a workaround, but a requirement for the router to work properly. if you don't set base[href] then we have no way of telling what is the root path of your app and all of the links and static resources in your app will be loaded from the wrong location (unless you use absolute paths).

[Siyfion]

@IgorMinar I wasn't until @clkao pointed it out, but now I am. Perhaps this needs to be made a bit clearer somewhere in the documentation... Plus I'd put the tag into the Yeoman generator-angular project with a dummy value, as that'll force people to notice!

[IgorMinar]

so it turns out that base[href] approach has some issues. see the commit message of 2bc62ce for more info.

[geddski]

Here's an idea that would help: #2805