Hi, All! Usually, we want to use $httpParamSerializerJQLike along with application/x-www-form-urlencoded. $httpParamSerializerJQLike uses encodeUriQuery which do not encode these symbols (@ : $ , ; +) under the hood, however, we should encode those symbols in accordance with w3c recommendation <https://www.w3.org/TR/html5/forms.html#application/x-www-form-urlencoded-encoding-algorithm> to x-www-form-urlencoded encoding algorithm. You ignore the recommendation and follow the rules of rfc3986 <https://tools.ietf.org/html/rfc3986>. Here are your specs <https://github.com/angular/angular.js/blob/cc793a1364d5861afd262846ef4c621812ea353c/test/AngularSpec.js#L1587>. It makes $httpParamSerializerJQLike useless to use with application/x-www-form-urlencoded.
So, why do you apply rfc3986 <https://tools.ietf.org/html/rfc3986> to $httpParamSerializerJQLike? Thanks! -- You received this message because you are subscribed to the Google Groups "Angular and AngularJS discussion" group. To unsubscribe from this group and stop receiving emails from it, send an email to angular+unsubscr...@googlegroups.com. To post to this group, send email to angular@googlegroups.com. Visit this group at https://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
