query string in resource urls is not handled correctly

[akonsu]

my service has to use a query string due to limitations on the server that runs classic ASP:

angular
  .module('myServices', ['ng', 'ngResource'])
  .factory('Item', ['$resource',
     function ($resource) {
         return $resource('/api/?p=item/:id');
     }]);

and I want to add extra query string parameters to it:

Item.query({test: 123}, on_success, on_error);

but the resulting url is

/api/?p=item?test=123

[erikwco]

Hi Pal, i already had this error and i solved in this way

i created a service

var servs = angular.module('app.services', ['ngResource']);

servs.factory('Products',function($resource){
  return $resource('/data/products.asp?productId=:productId',{},{
    query:{method:'GET',params:{productId:'0'},isArray:true}
    });
});

using get method you send parameters in query string and from the controller

function ProductDetailCtrl($scope,$routeParams,Products){
    $scope.product = Products.query({productId: $routeParams.productId, action: 'new'}, function(product) {
      $scope.product = product[0];
    });
}

the result is

/data/products.asp?productId=10&action=new

hope that's helps

Erik!
(Sorry for my english, greetings from El Salvador)

[akonsu]

Your code is very similar to mine. I tried yours and it gave me similar results. Two question marks in the URL. I am using Angular version 1.0.2.

[erikwco]

hi, i already checked and i'm using Angular 1.1.0, can you update your angular version to 1.1.0 and try?

[arkarkark]

I'm also seeing this problem. the workaround works, but then you need to define the params for each one of your methods in the resource rather than relying on the super nice defaults that are set up for you.

looks like it's line 326 in resource.js:
return url + (query.length ? '?' + query.join('&') : '');

https://github.com/angular/angular.js/blob/master/src/ngResource/resource.js

(h/t to PavelJ!)

[btford]

As part of our effort to clean out old issues, this issue is being automatically closed since it has been inactivite for over two months.

Please try the newest versions of Angular (1.0.8 and 1.2.0-rc.1), and if the issue persists, comment below so we can discuss it.

Thanks!